> ## Documentation Index
> Fetch the complete documentation index at: https://rollout.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix an entity that is not configured to sync

> Resolve 'This credential is configured to not sync' errors and enable missing data types.

If a request returns an error such as this, the credential is not configured to sync the requested type of data:

```json theme={null}
{
  "errorMessage": "This credential is configured to not sync Notes."
}
```

For notes and tasks, this is an HTTP `400` response. It does not by itself mean the user's login or API key is invalid. Rollout calls each type of data an **entity**; some entities, including notes and tasks, need to be enabled explicitly.

## 1. Check which connection you are using

Find the credential ID sent in your request's `X-Rollout-Credential-Id` header. Open that credential in the dashboard and confirm it belongs to the intended connected account. Updating a different credential will not fix this request.

## 2. Check connector support

In **Entities To Sync**, look for the type named in the error, such as `notes` or `tasks`. The dashboard lists the connector's syncable types.

If the type is unavailable, enabling it in code cannot add connector support. Check the connector's capabilities or [contact support](/docs/contact.md). An error saying `Functionality not supported for this connector.` is a different condition from an entity being disabled.

## 3. Enable the entity on the existing credential

Select the type in **Entities To Sync**, retain the other types your app needs, and click **Save**. You can also use the [Update Credentials API example](/docs/advanced-guides/controlling-which-records-sync-with-rollout.md#through-the-api).

> [!WARNING]
>
> An API update replaces your app's optional selection for that credential. Include all optional types you still need, not just the newly enabled type.

You do not need to delete and recreate the connection. Adding `entitiesToSync` to your frontend component alone does not update an existing credential.

## 4. Allow the sync to run, then retry

Saving the settings resets the connection's sync. Allow time for the newly enabled data to be fetched, then retry with the same credential ID. Enabling a type does not guarantee that the connected account contains records of that type.

| What you see | What to do |
| - | - |
| `This credential is configured to not sync…` | Check the selection on the credential used by your request. Waiting alone does not enable it. |
| `Functionality not supported for this connector.` | Check connector support for the requested operation. |
| `409` indicating data is not ready | Allow the sync to progress and retry. Inspect the error message; not every `409` is a sync-readiness error. |
| A successful response with no records | Confirm the source account contains matching records, check request filters, and check sync progress. |

## Prevent it on future connections

Choose your defaults in [dashboard Settings → Default Entities To Sync](/docs/advanced-guides/controlling-which-records-sync-with-rollout.md#set-defaults-in-dashboard-settings), and omit `entitiesToSync` from your component to use them for new connections. This does not update existing credentials.

Alternatively, pass an explicit selection in code. It takes precedence over the dashboard defaults:

```tsx theme={null}
<CredentialsManager entitiesToSync={{ notes: true, tasks: true }} />
```

Keep this selection in every version of your connection UI, including custom `CredentialForm` or `AddCredentialForm` components. See [Choose what data to sync](/docs/advanced-guides/controlling-which-records-sync-with-rollout.md) for defaults and configuration details.

When handling API failures, read `errorMessage` so the actionable error reaches your logs or UI:

```typescript theme={null}
const data = await response.json();
if (!response.ok) {
  throw new Error(data.errorMessage || data.error || `Request failed (${response.status})`);
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.