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

# Salesforce Data 360 Troubleshooting

> Troubleshoot common Salesforce Data 360 database connector issues in Collate, including connected app authentication and API access errors.

## Troubleshooting

### Workflow Deployment Error

If there were any errors during the workflow deployment process, the
Ingestion Pipeline Entity will still be created, but no workflow will be
present in the Ingestion container.

* You can then Edit the Ingestion Pipeline and **Deploy** it again.
* From the Connection tab, you can also Edit the Service if needed.

## Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in Collate. Below are some of the most frequently observed troubleshooting scenarios.

## How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in Collate:

1. **Navigate to Connections**
   Go to **Connections** > **Service Type** (e.g., Database) in the Collate UI.

2. **Select a Service**
   Choose the specific service for which you want to enable debug logging.

3. **Access Agents Tab**
   Go to the **Agents tab** and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.

4. **Enable Debug Logging**
   In the configuration dialog, enable the **Debug Log** option and click **Next**.

5. **Schedule and Submit**
   Configure the schedule if needed and click **Submit** to apply the changes.

## Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

## Salesforce Data 360-Specific Issues

The following issues are specific to the Salesforce Data 360 database connector.

### Connection Test Fails on "CheckAccess" or Authentication

Collate authenticates with the Consumer Key and Consumer Secret from your Salesforce connected app using the OAuth 2.0 client credentials flow. If the connection test fails before listing any data:

* Confirm the Consumer Key and Consumer Secret were copied correctly and have not been rotated in Salesforce.
* Confirm the connected app has the client credentials flow enabled and is granted the Data 360 (Data Cloud) API scopes.
* Check the **Salesforce Domain** value. Use `login` for production, `test` for a sandbox, or your My Domain subdomain for a custom domain. A wrong domain sends the login request to the wrong Salesforce URL.

### Connection Test Passes but No Data Spaces or Tables Are Ingested

The connection test lists the data spaces and the objects in the first one. If the test passes but ingestion returns nothing:

* Confirm the integration user the connected app runs as can see the data spaces and their Data Lake Objects, Data Model Objects, and Calculated Insights.
* Check your database, schema, and table filter rules. An overly broad exclude rule can filter out everything.

### Some Tables Are Missing After a Run

If a Data 360 API call fails while listing the objects in a schema, Collate skips deletion reconciliation for that schema so a transient failure is not mistaken for every object being removed. The missing objects are reported as warnings in the ingestion logs. Re-run the ingestion once the API is reachable again, and review the logs for the specific error.


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