# Development pausing 

Gadget automatically pauses inactive development environments after inactivity to conserve resources. This ensures that unused environments do not consume unnecessary resources.

| Plan name | Inactivity before pausing |
| --- | --- |
| Hobby | 15 minutes |
| Pro | 1 hour |
| Premium | 1 hour |

When a development environment is paused, it **stops processing requests**, and any external API call will fail until the environment is resumed (this includes Shopify webhooks and scheduled syncs). This behavior **does not** apply to your production environments — live apps remain online at all times.

## Unpausing Your Environment 

To resume a paused development environment:

*   Log into the Gadget editor and access the paused environment.
*   If running Gadget locally, run `ggt dev` against your environment.

Once accessed, the environment automatically unpauses, and all requests will process as expected.

## Logs and Error messages 

There are two logs associated with environment pausing:

### When a request fails - GGT\_ENVIRONMENT\_PAUSED 

If a request is made while the environment is paused, it will fail, and this error log will be generated:

```json
{
  "error": "GGT_ENVIRONMENT_PAUSED",
  "paused_on": "2025-03-25T12:00:00Z",
  "message": "Request failed, your environment is paused and temporarily unavailable. Developer must log into the Gadget Editor to unpause the app.",
  "code": 540
}
```

*   `paused_on` → The timestamp indicating when the environment was paused

This log helps developers identify when a request failed.

### When the Environment is unpaused 

Once the environment is accessed and resumes operation, this log is generated:

```json
{
  "message": "Environment unpaused. Your environment is now active.",
  "paused_during": {
    "start": "2025-03-24T12:00:00Z",
    "end": "2025-03-25T12:00:00Z"
  }
}
```

*   `paused_during.start` → The timestamp when the environment first paused.
*   `paused_during.end` → The timestamp when the environment resumed.

This log provides a clear history of when the environment was inactive before it became active again.

## Syncing Shopify data after unpausing 

If you have a Shopify connection, any webhooks that fired or scheduled syncs that occurred while the app was paused were not processed. This means your data may be out of sync with Shopify.

To bring your environment data back in sync with Shopify, run a manual sync using using `syncSince` to fetch all changes since your environment was paused:

```typescript
await api.shopifySync.run({
  domain: "MY_COOL_STORE.myshopify.com", //Shop Domain
  shop: {
    _link: "12345678901", //Shop ID
  },
  syncSince: "2025-03-24T12:00:00Z", //Paused start dateTime
});
```

Once the sync is complete, your development environment will reflect the latest Shopify data.