You are here:
Why is my recipe or data sync job running out of time or being killed?
A recipe or data sync job can fail because the integration user can’t authenticate.
If you receive one of these error messages, it typically indicates a temporary lack of server resources. Rerunning the job usually resolves the issue.
-
Queue wait time exceeded limit. -
Job killed due to inactivity.
However, if your jobs fail repeatedly, you could have an authentication issue with the integration user. If the integration user can’t authenticate, the job waits in the queue until it expires or a cleanup process kills it. Authentication issues for the integration user can also affect a dataflow.
To troubleshoot an authentication issue, check these settings.
| Setting | Description |
|---|---|
| Analytics Cloud Integration User profile settings | The integration user is associated with an Analytics Cloud Integration User profile. Make sure that this profile doesn’t have login IP ranges, login hours, or multi-factor authentication enabled or defined. |
| Insights app | The integration user must have the Insights app in their OAuth apps list. |
| API client allowlisting | If you’ve enabled For admin-approved users, limit API access to only allowlisted connected apps, check that the integration user’s Analytics Cloud Integration User profile has the Use Any API Client system permission. |
If these checks don’t resolve your issue, look for other authentication restrictions in your org and ensure the integration user can authenticate.
