Comprehensive guide to handling API errors and retry mechanisms
Workflows can sometimes encounter interruptions due to paused, stopped, or shutdown statuses. Understanding why retries are important, when to retry, and how to do it effectively is essential for maintaining smooth operations and minimizing delays.
Using account rotation for search and enrichment actions ensures retries are seamless and done on our end.
Here’s how it works:
To enable Account Rotation, include this parameter when launching a workflow via API:
Workflows may pause due to integration issues, such as a broken cookie. Here are several ways to address the issue.
Resume all paused jobs at once while updating the user’s cookies:
Use the POST Add or Update an Integration Account endpoint and set resume_paused_jobs
to true
:
Request payload example:
To retry Specific Runs only: Update the user account cookies and use the POST Retry a Run endpoint:
Example payload:
For Shared Accounts:
Share this link with the account owner to refresh the cookie manually: https://app.captaindata.co/integrations/linkedin/accounts/{user_id}
.
This avoids waiting for Captain Data’s (or your own) Chrome extension to update it (updates occur every 2 hours).
And then, use the POST Retry a Run endpoint.
For more information, see the related article: Add & Managing Users.
Canceling Jobs:
You realize you did a mistake or the job is stuck for too long, you can cancel it using the POST Cancel a Run endpoint. This allows you to quickly stop any ongoing processes that are no longer needed.
Restarting Stopped Jobs:
After addressing the issue, restart the job using the POST Retry a Run endpoint. Ensure all necessary updates, such as fixing inputs or updating account credentials, are completed before retrying.
Polling for Shutdown Jobs: Stop polling as soon as a job enters the Shutdown status; there’s no need to continue.
If you believe the inputs should work or need assistance, please contact us with all relevant details.
All inputs failed. Please correct them before retrying your job.
, it typically means the provided inputs are invalid.
In this case, check Inputs - To gain more details regarding this error by inputs, use the Get a Run’s Inputs:
By understanding and using retries effectively, you can overcome interruptions and keep your workflows on track.
Here’s a list of the most common errors you could come across; classified by API.
Users API
POST
Create or Update a UserIntegration Accounts API
POST Add or Update an Integration Account
POST Add or Update an Integration Account
POST Add or Update Integration Account
user_uid
POST Add or Update Integration Account
POST Add or Update Integration Account
Jobs and Workflows API
POST Launch a Workflow
POST Launch Workflow
with parameter account_rotation=true
POST Launch Workflow
with parameter account_rotation=false
LinkedIn Automation Specific Errors
{"code":"CANT_RESEND_YET"}
.POST Launch a Workflow
POST Launch Workflow
POST Launch Workflow
POST Launch Workflow
Comprehensive guide to handling API errors and retry mechanisms
Workflows can sometimes encounter interruptions due to paused, stopped, or shutdown statuses. Understanding why retries are important, when to retry, and how to do it effectively is essential for maintaining smooth operations and minimizing delays.
Using account rotation for search and enrichment actions ensures retries are seamless and done on our end.
Here’s how it works:
To enable Account Rotation, include this parameter when launching a workflow via API:
Workflows may pause due to integration issues, such as a broken cookie. Here are several ways to address the issue.
Resume all paused jobs at once while updating the user’s cookies:
Use the POST Add or Update an Integration Account endpoint and set resume_paused_jobs
to true
:
Request payload example:
To retry Specific Runs only: Update the user account cookies and use the POST Retry a Run endpoint:
Example payload:
For Shared Accounts:
Share this link with the account owner to refresh the cookie manually: https://app.captaindata.co/integrations/linkedin/accounts/{user_id}
.
This avoids waiting for Captain Data’s (or your own) Chrome extension to update it (updates occur every 2 hours).
And then, use the POST Retry a Run endpoint.
For more information, see the related article: Add & Managing Users.
Canceling Jobs:
You realize you did a mistake or the job is stuck for too long, you can cancel it using the POST Cancel a Run endpoint. This allows you to quickly stop any ongoing processes that are no longer needed.
Restarting Stopped Jobs:
After addressing the issue, restart the job using the POST Retry a Run endpoint. Ensure all necessary updates, such as fixing inputs or updating account credentials, are completed before retrying.
Polling for Shutdown Jobs: Stop polling as soon as a job enters the Shutdown status; there’s no need to continue.
If you believe the inputs should work or need assistance, please contact us with all relevant details.
All inputs failed. Please correct them before retrying your job.
, it typically means the provided inputs are invalid.
In this case, check Inputs - To gain more details regarding this error by inputs, use the Get a Run’s Inputs:
By understanding and using retries effectively, you can overcome interruptions and keep your workflows on track.
Here’s a list of the most common errors you could come across; classified by API.
Users API
POST
Create or Update a UserIntegration Accounts API
POST Add or Update an Integration Account
POST Add or Update an Integration Account
POST Add or Update Integration Account
user_uid
POST Add or Update Integration Account
POST Add or Update Integration Account
Jobs and Workflows API
POST Launch a Workflow
POST Launch Workflow
with parameter account_rotation=true
POST Launch Workflow
with parameter account_rotation=false
LinkedIn Automation Specific Errors
{"code":"CANT_RESEND_YET"}
.POST Launch a Workflow
POST Launch Workflow
POST Launch Workflow
POST Launch Workflow