Common Integration Errors and Resolution in BoldDesk
This article helps you troubleshoot common integration-related errors that may occur when using automations, Marketplace apps, webhooks, external integrations, file operations, authentication workflows, and ticket-related actions in BoldDesk. These errors are typically caused by missing required fields, invalid values, permission restrictions, configuration issues, subscription limitations, authentication failures, or integration-specific validation requirements. Use this guide to understand why an error occurs and the recommended steps to successfully complete the integration operation.
Some error messages contain placeholders such as {0}. These placeholders are automatically replaced with the relevant integration, module, application, account, or resource name when the error is displayed.
Common Integration Error Categories
Below are the common integration error categories with their resolutions.
| Error Category | Common Error Messages | Recommended Resolution |
|---|---|---|
| Required Field Errors | Category not selected, Priority not selected, Access token required, API key required, Marketplace app ID required, Integration account required, Field mapping required, Project mapping required, Organization mapping required, Token required, Webhook required, and other similar required-field errors. |
Ensure all required fields, IDs, credentials, mappings, and configuration settings are provided before retrying the operation. |
| Invalid Value Errors | Priority Invalid, Type Invalid, Status Invalid, Invalid User, Invalid URL, Invalid email ID, Invalid webhook URL, Invalid integration settings, Invalid condition data, Invalid app ID, Invalid team, and other similar validation errors. |
Verify the value format, ensure referenced resources exist, and use supported values before retrying. |
| Authentication and Authorization Errors | Authentication failed, Authentication failed due to token expired, The token has expired. Please reauthorize the {0}, {0} integration authentication failed, The user is not authorized to revoke integration, permission-related errors. |
Reauthenticate the integration, refresh expired credentials or tokens, and verify the user has the required permissions. |
| Resource Not Found Errors | User account not found, Integration not found, Marketplace app not found, Webhook ID not found, Notification not found, Store not found, {0} account not found, Category does not exist, Group does not exist, and other similar not-found errors. |
Verify the referenced resource exists, confirm the identifier is correct, and ensure you have access to the resource. |
| Duplicate Resource Errors | Integration already exists, Store already exists, Domain name already exists, The accounts can't be duplicated, The field mapping can't be duplicated, The projects can't be duplicated, and other duplicate-resource errors. |
Remove duplicate entries or update the existing resource instead of creating a new one. |
| Subscription and Licensing Errors | Your current subscription plan does not include support for this feature, Your current subscription plan is suspended, Custom app quota exceeded, Marketplace app quota exceeded, Display fields limit exceeded, File size exceeds the allowed limit, and other quota or plan-limit errors. |
Reduce resource usage, remove unused items, renew the subscription if required, or upgrade to a plan that supports the feature. |
| Ticket and Automation Validation Errors | Validation failed, Due Date Invalid, Automation user is invalid, Ticket Status does not exist or you don't have permission, AI Assist is required to use Auto-Merge Tickets, Merging rule required, and related workflow validation errors. |
Verify automation settings, confirm AI Assist requirements are met, configure a valid automation user, and validate workflow inputs. |
| Integration Processing Errors | An error occurred when processing {0} integration, An unidentified error occurred while retrieving the {0} record count, An unidentified error occurred while retrieving the {0} record details, Retry message, Account successfully verified, No changes found. |
Review integration logs, verify configuration and connectivity settings, and retry the operation after resolving identified issues. |
| File and Attachment Errors | Unable to upload the file, Unable to delete the file, Attachment is invalid, File type is not supported, Files and FileURLs cannot be provided together. |
Verify the file type, attachment format, upload method, and file size before retrying. |
| Webhook and Notification Errors | Invalid webhook URL, Invalid webhook condition, Invalid external webhook, Event data validation failed, Notifications cannot be activated while the app is disabled, Notifications cannot be added while the app is disabled, and similar webhook or notification errors. |
Verify webhook configuration, notification settings, destination endpoints, and ensure the associated Marketplace app is enabled. |
Troubleshooting Checklist
Before contacting support:
- Verify all required fields are populated.
- Confirm credentials and authentication tokens are valid.
- Ensure referenced resources exist and are accessible.
- Review integration mappings and webhook settings.
- Check for duplicate configurations.
- Verify subscription limits have not been exceeded.
- Reauthenticate integrations if tokens have expired.
- Review integration logs for additional error details.
- Retry the operation after correcting the identified issue.
Frequently Asked Questions
-
Why am I receiving a validation error?
Validation errors occur when submitted data is missing, invalid, or does not meet the expected format or configuration requirements. -
What should I do if an integration fails unexpectedly?
Review the integration logs, verify authentication, validate the request data, and retry the operation after resolving any identified issues. -
Why am I seeing a quota exceeded error?
Quota-related errors occur when the number of configured resources exceeds the limits supported by your subscription plan. -
How do I resolve authentication failures?
Verify credentials, refresh expired tokens, reauthorize the integration, and confirm that the connected account has the required permissions. -
What does “resource not found” mean?
The requested account, integration, application, webhook, or other referenced record either does not exist, has been removed, or is inaccessible with the current permissions. -
Why can’t I enable notifications?
Notification-related errors typically occur when the associated Marketplace app is disabled, required configuration is missing, or webhook validation fails.
