Crawler failure notifications
Workato GO crawlers fetch data from connected sources, such as Google Drive, Confluence, Slack, and more. You can configure crawler notifications to send emails when a crawler fails.
Configure notifications
You can create a property with a list of emails that receive crawler failure notifications in Workato GO.
Complete the following steps to configure crawler failure notifications:
Sign in to your Workato GO account.
Expand the Admin menu in the sidebar and click Advanced.
Click Add Organization Property.
Enter a name for your property. For example: crawler.failure_notification_emails
Enter the email addresses that should receive notifications. You must separate user email addresses with commas. For example:
alex@example.com,caroline@example.com,carlos@example.comClick Submit.
Crawler failure error codes
Workato GO returns specific error codes when crawlers fail to access or process data. You can use these codes to identify the root cause of failures and take corrective action. The following tables list common error codes by data source, their descriptions, and the required actions:
General error codes
| Code | Description | Required action |
|---|---|---|
| GENERAL_1 | Network connection timeout | The crawler couldn't reach the target service. |
| GENERAL_2 | DNS resolution failed | The website URL couldn't be resolved. Verify that your data source URL is correct. |
| GENERAL_3 | Invalid crawler configuration | Your data source is missing required settings. Review and update your configuration. |
| GENERAL_4 | Service temporarily unavailable | The service is temporarily unavailable. Try again later. |
| GENERAL_5 | Record not found | The data source may have been deleted. Verify it still exists in your workspace. |
| GENERAL_6 | API rate limit exceeded | The target service is limiting requests. The crawler automatically retries after the rate limit resets. |
| GENERAL_7 | API endpoint not found | The API URL in your configuration may be incorrect. Update your data source settings. |
Confluence error codes
| Code | Description | Required action |
|---|---|---|
| CONFLUENCE_1 | Confluence authentication failed | Your API token is expired or invalid. Generate a new token in Confluence and update your data source. |
| CONFLUENCE_3 | Insufficient Confluence permissions | The Confluence user doesn't have access to the requested content. Check the user's space and page permissions. |
| CONFLUENCE_99 | Unknown Confluence error | An unexpected error occurred. Contact support if the issue persists. |
Custom web data source error codes
| Code | Description | Required action |
|---|---|---|
| WEB_1 | Web crawler authentication failed | The website requires login credentials. Only publicly accessible websites are supported. |
| WEB_99 | Unknown web crawler error | An unexpected error occurred. Contact support if the issue persists. |
Google Drive error codes
| Code | Description | Required action |
|---|---|---|
| GDRIVE_1 | Google Drive service account authentication failed | Service account credentials are invalid or expired. Re-upload your credentials JSON file. |
| GDRIVE_3 | Insufficient Google Drive permissions | The service account doesn't have access to the files or folders. Share the files or folders with your service account email. |
| GDRIVE_99 | Unknown Google Drive error | An unexpected error occurred. Contact support if the issue persists. |
Highspot error codes
| Code | Description | Required action |
|---|---|---|
| HIGHSPOT_1 | Highspot authentication failed | Your API credentials are invalid or expired. Update your Highspot API credentials in the data source. |
| HIGHSPOT_3 | Insufficient Highspot permissions | The API user doesn't have the required access. Contact your Highspot administrator to grant permissions. |
| HIGHSPOT_99 | Unknown Highspot error | An unexpected error occurred. Contact support if the issue persists. |
Jira error codes
| Code | Description | Required action |
|---|---|---|
| JIRA_1 | JIRA authentication failed | Your API token or credentials are invalid. Generate a new API token in JIRA and update your data source. |
| JIRA_3 | Insufficient JIRA permissions | The JIRA user doesn't have access to the requested project. Check the user's project permissions. |
| JIRA_99 | Unknown JIRA error | An unexpected error occurred. Contact support if the issue persists. |
People directory error codes
| Code | Description | Required action |
|---|---|---|
| PEOPLE_1 | People directory authentication failed | Your Okta or Google Workspace connection has expired. Re-authenticate in your data source settings. |
| PEOPLE_3 | Insufficient directory permissions | The connected account doesn't have directory read permissions. Ask your IT admin to grant access to the necessary permissions. |
| PEOPLE_99 | Unknown people sync error | An unexpected error occurred. Contact support if the issue persists. |
Slack error codes
| Code | Description | Required action |
|---|---|---|
| SLACK_1 | Slack authentication failed | Your bot token is invalid or the app was uninstalled. Reconnect Slack in your data source settings. |
| SLACK_3 | Missing required Slack OAuth scopes | The Slack app needs additional permissions. Re-authorize the Slack connection with the required scopes. |
| SLACK_99 | Unknown Slack error | An unexpected error occurred. Contact support if the issue persists. |
Last updated: