Task Integrations error codes
Every public API error code emitted by Task Integrations, with its HTTP status, its type and a page per code.
Error codes emitted by Task Integrations. Each code links to its own page with the cause and the action to take.
| Code | Type | HTTP | Description |
|---|---|---|---|
forge_account_link_rejected | invalid_request_error | 422 | Only personal GitHub accounts can be linked. GitLab and Gitea do not use linked accounts: they connect with the access token of the project integration. |
forge_account_not_linked | invalid_request_error | 422 | The operation acts on your behalf in the forge —for example, to list your GitHub repositories— and you have not linked your account on that forge to your user yet. |
forge_credentials_rejected | invalid_request_error | 422 | The GitLab or Gitea instance rejects the given address or credential. The subcode says why: not_a_forge_instance, redirected, repository_not_found, insufficient_permissions or unauthorized. |
forge_oauth_state_invalid | invalid_request_error | 422 | The forge link could not be completed: the authorisation state has expired, was already used, is not valid or belongs to another user or company. |
forge_repository_access_denied | authorization_error | 403 | Your linked GitHub account does not allow connecting that repository, or the repository does not exist; the answer is the same in both cases so that other people's repositories are not revealed. |
forge_repository_bound_elsewhere | conflict_error | 409 | The repository is already connected to another active project of the company. A repository feeds a single project, so that each issue or pull request ends up in a single task. |
forge_secret_rotation_not_supported | invalid_request_error | 422 | This integration has no webhook secret of its own to rotate: GitHub integrations sign with the GitHub App secret, and rotation only exists for GitLab and Gitea integrations. |
forge_token_required | invalid_request_error | 422 | The forge instance URL is being changed without a new token. The stored token is never sent to an address other than the one it was issued for, so that it does not end up on a foreign server. |
forge_webhook_signature_invalid | authentication_error | 401 | The forge webhook delivery could not be authenticated: the signature does not match the integration secret, or the integration does not exist. No event was processed. |
forge_workflow_rule_column_invalid | invalid_request_error | 422 | The rule's target column does not belong to the integration's project; a non-existent column, one from another project or one from another company all answer the same. |
forge_workflow_rule_not_found | not_found_error | 404 | The rule that moves tasks between columns on a forge event (for example, when a pull request is merged) does not exist or belongs to another company; both cases answer the same. |
github_app_not_configured | invalid_request_error | 422 | The GitHub integration is not available on this server because its administrator has not configured the GitHub App. It is not a problem with your account or your permissions. |
import_credentials_rejected | invalid_request_error | 422 | The import source system rejected the supplied credentials with an unauthorised or forbidden response. Nothing was imported. |
import_run_already_active | conflict_error | 409 | An import from the same source into the same target is already running. Two simultaneous imports would create duplicate tasks, so the second one is not started. |
integration_destination_not_allowed | invalid_request_error | 422 | The company egress policy does not allow connecting to that address: for security, private or internal destinations are blocked unless the company has allowed them. The error does not repeat the rejected URL. |
project_integration_already_connected | conflict_error | 409 | The project already has an integration of that type, or is already connected to another repository. Each project accepts one integration per type, so that events are not duplicated. |
project_integration_not_found | not_found_error | 404 | The project integration does not exist or belongs to another company; both cases answer the same. Forge and chat integrations are managed only from the web application, not from the v1 API. |
task_import_run_not_found | not_found_error | 404 | The given import does not exist or belongs to another company; both cases answer the same. Each import has its own identifier, different from the target project's. |
Related
Error codes by category
Find an error by the category that emits it.
Full reference table
All codes, HTTP statuses, types and descriptions in one reference.
Error model
Interpret the error envelope and handle errors by code.