Marketplace Configuration Errors and Resolution in BoldDesk

This article helps you identify and resolve common Marketplace integration and configuration errors in BoldDesk. These errors can occur when configuring account mappings, installing or managing Marketplace apps, validating integration settings, processing integration events, or handling authentication and delivery failures. Use the error reference, troubleshooting guidance, and FAQs in this article to understand why an error occurs and the recommended steps to restore normal integration functionality.

Some error messages contain placeholders such as {0}, {1}, and {2}. These placeholders are automatically replaced at runtime with the relevant integration, account, brand, user, URL, or other contextual values.

Account Mapper Validation Errors

These errors occur when creating, updating, or retrieving an account mapper resource.

Error message	When it displays	How to resolve
`The {0} number is already linked to another brand.`	Creating an account mapper when the same number is already mapped to a different brand.	Use a different number, or update the existing account mapper that currently owns the number.
`Invalid brand id.`	The provided account mapper `brand id` value is malformed or does not pass validation.	Verify the `brand id` format and value, then retry.
`Brand id required.`	The account mapper `brand id` field is missing in the request.	Provide the required `brand id` field and retry.
`Invalid category id.`	The provided `category id` is malformed or invalid.	Verify the `category id` format and value, then retry.
`Category id required.`	The `category id` field is missing for the account mapper.	Provide the required `category id` field and retry.
`Configuration required.`	The account mapper `configuration` field is missing.	Provide the required `configuration` object/field in the request payload.
`Invalid form id.`	The provided `form id` is malformed or invalid.	Verify the `form id` format and value, then retry.
`Form id required.`	The request is missing the required `form id` field.	Provide the required `form id` field and retry.
`Invalid group id.`	The provided `group id` is malformed or invalid.	Verify the `group id` format and value, then retry.
`Group id required.`	The request is missing the required `group id` field.	Provide the required `group id` field and retry.
`Name must not exceed 100 characters.`	The account mapper `name` exceeds the maximum length (100).	Shorten the account mapper name to 100 characters or fewer.
`Name required.`	The account mapper `name` is null or empty.	Provide a non-empty `name` value and retry.
`No changes found.`	An update request does not contain any effective changes compared to the stored configuration.	Modify one or more fields meaningfully, then retry the update.
`Invalid status.`	The provided `status` value is malformed or not supported.	Verify the `status` value and format, then retry.
`Status is required.`	The account mapper `status` is missing or empty.	Provide the required `status` value and retry.
`Target phone number required.`	The account mapper `target phone number` is missing or empty.	Provide the required target phone number value and retry.
`Account not found.`	The requested `marketplaceaccountmapper` resource cannot be found or retrieved.	Confirm the account mapper ID/reference is correct and the resource exists.

Marketplace App and Integration Identification Errors (AppId / Installation)

These errors occur when Marketplace integration requests reference an app/integration that is missing, uninstalled, or not resolvable.

Error message	When it displays	How to resolve
`Marketplace app ID required`	An integration-related request is missing the `AppId` field. (This message appears in multiple locations with or without a trailing period.)	Provide the `AppId` of the installed Marketplace app in the request payload and retry.
`Integration not found`	The supplied `AppId` (or derived integration reference) does not resolve to any installed Marketplace app integration.	Install the relevant Marketplace app, provide a valid `AppId`, and retry. If access is restricted, contact an admin to grant access.
`Marketplace app not found`	The referenced Marketplace app cannot be located (for example, for a `CloudStorageTypeId` mapping) or the app was uninstalled.	Install or re-install the corresponding Marketplace app, or select a valid/active app type identifier and retry.

Integration Configuration and Payload Validation Errors

These errors occur when an integration is installed/refreshed/updated with invalid settings, or when events sent into the integration fail validation.

Error message	When it displays	How to resolve
`Invalid integration settings`	The configuration supplied to an integration install/refresh/update operation is invalid (missing required fields, wrong formats, or unsupported values).	Review the integration configuration in Admin > Marketplace, correct required fields and formats, then retry the operation.
`Invalid integration data`	The integration receives event/payload data that fails validation, returned as a field error.	Verify the source event payload, ensure all required fields are populated and correctly formatted, then retry.
`Invalid team`	The supplied `TeamId` is malformed or not linked to the integration.	Provide a valid, active team identifier that is linked/allowed for the integration, then retry.
`External User Id Required`	An external-user creation request is missing `ExternalUserId`.	Provide the `ExternalUserId` from the third-party system and retry.
`{0} account not found`	The integration cannot locate the third-party account record.	Ask the user to sign in again and verify or correct the account mapping.

Integration Execution Failures (Trigger vs Action)

These errors indicate that an integration was found and invoked, but execution failed. They are not the same as validation errors (for example: missing AppId).

Error message	When it displays	How to resolve
`Integration Trigger Failed`	Returned as the ResponseType or Result type when an integration trigger execution fails for reasons unrelated to data validity.	Inspect trigger logs, verify integration configuration, and retry. Escalate to an admin if the issue persists.
`Integration Action Failed`	Returned as the ResponseType or Result type when an integration action (post-trigger processing) fails.	Inspect action logs, verify integration configuration, and retry. Escalate if the issue persists.

Admin E-mail and Audit-log Messages (Integration Failure and Auto-deactivation)

These messages are used as notification templates and audit log entries when integrations encounter authentication errors or repeated delivery failures.

Authentication Failure Notification (E-mail Body)

Error message (template):
Hi Team, The {0} integration failed due to an authentication error. Please evaluate and correct the issues listed in the link below, {1}/agent/admin/audit-logs/integration-failure-logs Thanks, The {2} Team

When it displays: Used as the e-mail body sent to admins when an integration fails due to authentication.

How to resolve

Open the integration failure logs at the provided URL.
Fix the authentication issue indicated by the logged error (for example: re-authorize, refresh credentials, update expired tokens).

Auto-deactivation Notification (E-mail Body)

Error message (template):
Hi Team, Due to a series of delivery failures, the integration {0} has been temporarily deactivated. Please verify that the destination URL is working and resolve the integration errors which are listed in the below link. {1}/agent/admin/audit-logs/integration-failure-logs After resolving the integration errors, you can activate this integration from inactive tab of in MyApps page. Thanks, The {2} Team

When it displays: Used as the e-mail body sent to admins when an integration is auto-deactivated after repeated delivery failures.

How to resolve

Validate the destination endpoint (for example: destination URL availability).
Resolve the underlying integration errors listed in the integration failure logs.
Re-activate the integration from the inactive tab in MyApps after the errors are fixed.

Audit Log Entry for Per-user Revocation

Message	When it displays	How to resolve
`The integration with "{0}" has been temporarily revoked for the user "{1}" due to delivery failure.`	Written to the audit log when a user’s integration is automatically disabled after delivery failures.	No action is required for the audit entry itself. Ask the affected user to re-authorize the integration.

User-facing Revocation Message

Message	When it displays	How to resolve
`"{0}" integration has been temporarily revoked for the user "{1}".`	Shown when a per-user integration is auto-deactivated after delivery failures.	Ask the user to review the failure cause and perform the required remediation (for example: re-authorize, correct destination settings).

E-mail Subject Lines

Subject	When it displays	How to resolve
`The integration "{0}" temporarily deactivated`	Subject line when an integration is auto-deactivated.	Review failure logs and resolve the delivery failures before re-activating.
`{0} integration authentication failed`	Subject line when an integration fails authentication.	Restore valid authentication (for example: re-authorize or update credentials) and retry.

Frequently Asked Questions

What does {0} mean in an error message like The {0} number is already linked to another brand.?
{0} is a runtime placeholder populated with a specific value (for example: a phone number or integration name). The placeholder is not part of the value you should submit.
Why do I see both Marketplace app ID required and Marketplace app ID required.?
Both are the same validation surfaced from different code paths. The remediation is the same: include a valid AppId in the request payload.
What is the difference between Invalid integration settings and Invalid integration data?
Invalid integration settings refers to the integration’s configuration (install/refresh/update). Invalid integration data refers to an event/payload sent to the integration that fails validation.
What should I do when I receive an e-mail saying an integration is temporarily deactivated?
Open the integration failure logs from the link in the e-mail, resolve the delivery failures (often endpoint availability or credentials), then re-activate the integration from the inactive tab in MyApps.
What does Account not found. refer to in Marketplace account mapper errors?
Account not found. indicates the marketplaceaccountmapper resource could not be retrieved. Verify the resource identifier and confirm the resource exists.
What does {0} account not found mean in an integration context?
The integration could not find the third-party account record. Typically the user must sign in again or the account mapping must be corrected.
Why does No changes found. appear when I submit an update?
The update request did not change any stored fields. Change at least one field value (for example: name, status, target phone number, or mapping configuration), then retry.
What should I do when I see Invalid team?
Provide a valid TeamId that is active and linked to the integration. If the team must be provisioned or linked, an admin must correct the integration/team association.

Was this article useful?

Dislike

Comments (0)