The following is a complete list of error messages. Error messages are displayed on the Activity screen. More details on specific errors can be found under Troubleshooting and in our FAQ.
An unexpected error has occurred.
Attempt to resolve error according to the specific error message.
The maximum number of allowable errors has been reached. Any errors encountered after the maximum number will be discarded.
The system has run out of memory. Services have been stopped.
The artifact association could not be imported as an existing artifact association conflicts with it.
Contact support for assistance.
Data migration required to run an updated version of Tasktop Hub was cancelled due to a configuration change or because Tasktop Hub was shut down.
None, data migration will be resumed automatically.
Migration cannot be completed as there are errors related to disabled repositories.
There was a network error when attempting to communicate with a repository.
If the problem persists, contact your network administrator.
An unexpected connector exception has occurred.
Attempt to resolve error according to the specific error message.
An exception has occurred during the execution of a connector operation.
Attempt to resolve error according to the specific error message.
An unexpected error has occurred while attempting to establish a connection with an LDAP directory.
Attempt to resolve error according to the specific error message.
An unexpected error has occurred while communicating with an LDAP directory.
Attempt to resolve error according to the specific error message.
The authentication state for a repository connection has expired.
Typically, the authentication state for a repository connection expires on a periodic basis and authentication will be retried automatically. If the error persists, verify that the repository credentials for the associated repository are correct.
The project configuration is not valid. This problem is usually caused by a project and/or type being deleted or renamed in the repository, but can also be caused by other problems, such as a change in user permissions within the repository.
There was an unexpected error while attempting to authenticate with a repository.
Attempt to resolve error according to the specific error message.
The project configuration is outdated.
The repository collection configuration is not valid. This problem is usually caused by a project and/or type being deleted or renamed in the repository, but can also be caused by other problems, such as a change in user permissions within the repository.
The high-level container (i.e. the type of container chosen when clicking Manage Projects on the Collections screen) has changed.
Before resolving this issue, please:
Once this issue is resolved, your artifact routing will be removed from any relevant integrations, and need to be manually reconfigured.
The artifact is locked by another user or process.
See the specific error message for details on what artifact is locked. Ensure that no other user or process is currently using the artifact, and retry the operation.
The repository connection could not be established due to an insecure connection.
The artifact union configuration is invalid.
The events processing for this repository may be delayed because the repositorys event rate limit is set too low.
The repository query could not be created.
An integration must contain at least one route.
An integration must satisfy the constraints of its style. This type of error should not happen when an integration is built using the UI.
See the detailed message for more details about the parts of the integration that are invalid.
Collections used in an integration must all be attached to the same model.
Repository Collections used in an integration must have a mapping to a model.
An integration must have a source collection.
An integration must have a target collection.
An integration failed to locate the artifact to be modified. This can be caused by:
See the detailed message for more details about the parts of the lookup that failed.
The filter used in the integration has become invalid.
An integration must specify a key identifier for the given collections. Key identifiers are used to determine how to locate artifacts in a target collection. They do this by specifying the field on the source model that contains the target artifact formatted id.
All specified routes of an integration must be configured.
The conditional routing configuration of the integration has become invalid.
The repository query used in the collection has become invalid.
Tasktop Hub is currently updating its operational data for an integration.
The artifact routing for this integration is invalid because a route endpoint no longer exists, or cannot be routed to (i.e. a more specific route endpoint must be selected).
The twinless artifact update for this integration is invalid.
An Enterprise Data Stream Integration must reference a single SQL collection.
An Enterprise Data Stream Integration must reference at least one Collection to be used as a source of artifacts.
Select a source Collection for the Integration that is in error.
An Enterprise Data Stream Integrations data Collection must be mapped to a model. This corresponds to the model desired to be reported on.
Add mappings for the Collection used in the Enterprise Data Stream Integration.
An Enterprise Data Stream Integration source Collection must be mapped to the same model as the target Collection.
Add relationship to the model for the source Collection used in the Enterprise Data Stream Integration
An Enterprise Data Stream Integrations Collection must have exactly one project.
An Enterprise Data Stream SQL Collections underlying database table is missing a required column.
Add the required column to the underlying database table. See error message for missing column id.
Tasktop Hub integration services cannot be started due to a problem with the license. This problem can be caused by running the software without a license, using features that are not included in the installed license, or by having an invalid or expired license.
This problem can be resolved by installing a valid license using the following steps:
The repository connection cannot be used because connections to repositories of this type are not enabled by the license.
This problem can be resolved by installing a valid license using the following steps:
The integration cannot be used because conditional field flow configurations exist in this integration but are not enabled by the license.
Perform one of the following:
The collection cannot be used because mappings using a field from an artifact union exist within this collection but are not enabled by the license.
Perform one of the following:
Tasktop Hub integration services cannot be started because secure password storage has not been configured and initialized.
The Tasktop Hub services restart is taking longer than expected.
The mapping cannot be applied since the mapping is not valid for the artifacts in the current context.
The collection model mapping is not valid due to inconsistencies between the collection schema, the model schema and the mapping.
An artifact could not be updated or created because one or more of its values are not valid. See the specific error message for details.
Artifact cannot be processed since it is currently in use. This temporary problem occurs when Tasktop Hub attempts to process changes to an artifact concurrently.
This error will resolve itself automatically, no user action required.
The field flow configuration is not valid due to inconsistencies between the the model schema and the field flow.
An artifact was created by an integration but some values on the artifact could not be set.
The resulting artifact has some field values that may not be correct.
The conflict resolution strategy configuration is invalid.
Artifact could not be processed as it did not meet any of the configured conditions on the Conditional Artifact Routing page.
An extension provided invalid values when attempting to transition an artifact.
An extension attempted to transition an artifact with the same transition more than once.
An extension completed with an error. See the specific error message for details.
Extensions complete with errors for one of two reasons:
A state transition extension is configured in a collection that has no model fields selected.
Either disable the state transition of the collection or select model fields for the state transition.
To select the fields for the state transition:
To disable state transitions in the collection:
One or more relationship links could not be resolved as part of a synchronization.
This problem occurs when two artifacts that link to each other are synchronized out of order.
This commonly occurs when one artifact (A) links to another (B), but the linked-to artifact B has not yet been synchronized.
When the copy of artifact A (A') is created in the target repository, a link to a copy of B (B') cannot be created at that time since B' has not yet been created.
This problem usually resolves itself once B' is created; the link from A' to B' is created once B' becomes available.
One or more relationship links could not be resolved as part of a synchronization.
This commonly occurs when one artifact (A) links to another (B), but the linked-to artifact B has more than one corresponding copy in the target repository. This can be caused by having separate synchronization integrations that cause B to be copied into the target repository.
An unexpected error occurred when creating the artifact. The artifact may or may not have been created.
The repository does not support artifact creation.
A state transition extension is configured in a collection that requires fields that are not configured in the model.
Either remove the missing fields in the state transition configuration, or ensure that the model has the required fields.
To add the fields to the model:
To change the required fields of the state transition extension from the collection:
The work item artifact could not be synchronized due to a missing or invalid route.
The artifact could not be synchronized because the target container could not be found.
A transition was attempted on an artifact but an error resulted.
The artifact may be in an incorrect state.
Either address the cause from the specific error message, or disable/reconfigure the state transition of the collection.
To disable/reconfigure state transitions in the collection:
The container associated with the parent container of this artifact could not be found.
For the artifact pair import to succeed, the associated integration must be running.
An error occurred when processing the output of an extension. See the specific error message for details.
Field value configuration required. The field type for a field in your integration has changed and its field values must be re-mapped.
The comment flow configuration is not valid. This can happen if a repositorys comment visibility support has changed.
The Conditional Field Flow configuration is not valid. This can happen if either a field or value is not resolvable in the model schema.
The test step model mapping is not valid due to inconsistencies between the test step schema, the test step model schema and the mapping.
The time entry model mapping is not valid due to inconsistencies between the time entry schema, the time entry model schema and the mapping.
Configuration delta table is unavailable as it is being migrated. This temporary problem may occur when a user attempts to access the list of configuration changes before the migration completes shortly after an upgrade.
The configuration delta table migration will complete as a background job, no user action required.
Failed to transform imported configuration change into change applicable for this instance due to missing elements.
Create the required missing elements before re-importing the configuration change.
A Gateway Collection has been used, but the collection is not configured as a source in an integration. The payload has been lost.
A Gateway Collection must configure the Relationship(s) fields to associate them with the repository having referenced artifacts.
A Gateway Collection must have a model configured.
A gateway collection has been configured with a payload transformation extension, which is not permitted by the current license.
Perform one of the following:
A Gateway Collection must use a token.
An error occurred while attempting to send an email.
The mail server rejected the client connection because it was not able to authenticate.
During database upgrade, one or more associations were discovered to have an invalid reference. The records that reference nonexistent associated records were logged and deleted.
Do not cancel this error or run the associated integration without consulting Tasktop Support. (https://links.tasktop.com/support)
An unexpected error has occurred. Check the specific error message for details.
Check the specific error message for details of the failure. If possible correct the problem described in the error message, or contact your administrator for assistance.
The entity was not found because the entity no longer exists on the server.
Ensure that the provided entity id is correct, and if not correct the id and try again.
The data provided was not valid. See the specific error message for details.
Correct the problem described in the specific error message and try again.
The connector kind was not found.
Ensure that the connector kind is specified correctly and try again.
The request entity was not valid JSON.
Ensure that the request payload is formatted as a valid JSON entity and try again.
Secure password storage has not been initialized.
Configure secure password storage via the settings page.
Error connecting to repository. See the specific error message for details.
Check the specific error message for details of the failure. If possible correct the problem described in the error message, or contact your administrator for assistance.
The request MIME attachment could not be accepted either due to a bad request or an I/O failure.
This problem can be caused by insufficient disk space or lack of write permissions in the Tasktop Hub application temporary directory.
Tasktop Hub has been stopped due to unrecoverable errors. See error log for more details.
Correct the problem described in the specific error message and restart.
The configuration database is unavailable.
Ensure the configuration database is online and can be reached and ensure Tasktop Hubs database settings are correct.
The provided connection settings are not valid. See the specific error message for details.
Correct the problem described in the specific error message and try again.
The configuration database is locked for maintenance and cannot be used.
Wait for the ongoing maintenance to complete.
The Configuration database is in use by another instance of the application.
If this is the Tasktop Hub instance which should be running, then shut down any other instances of Tasktop Hub using the same database and restart this instance. Otherwise shut down this instance of Tasktop Hub.
Temporary error connecting to repository. See the specific error message for details.
Retry your action. If the problem persists, contact your administrator for assistance.
The repository connection could not be established due to an insecure connection.
Configuration applicable to the current deployment is incomplete or invalid.
Contact Tasktop customer support.
The current user is not authorized due to a restriction in the license.
Contact your Tasktop Hub administrator.
Tasktop integration services cannot be started because the current license has expired.
Tasktop integration services cannot be started because the no license has been configured.
The application is starting up and cannot be accessed at this time.
Wait for the application to finish starting up
The connection settings for the operational database are inaccessible.
Ensure the tasktop-db.json file is correctly formatted and the Tasktop Hub user has permission to read it.
The history page is not available before the necessary data migrations are complete.
Wait for the migrations to complete.
The repository connection will be disabled until it is manually enabled.
Changes to an artifact cannot be propagated to the corresponding artifact in the alternate repository of a synchronization integration since the target artifact has been removed.
A field conflict was detected when synchronizing artifacts. A field conflict occurs when the value of a field that is set to flow bidirectionally conflicts across your repositories.
The synchronization of these artifacts was halted with an error because a conflict resolution strategy of Error Upon Conflict was configured and the system was unable to propagate
the value from either artifact without overwriting a change from the other artifact.
A conflict was detected when synchronizing artifact containment. A conflict occurs when one or more containers of synchronized artifacts is changed for both artifacts.
Unable to find a new value for an unchanged dependent field.
OR
OR
Multiple matching containers were found when attempting to match containers.
The integration cannot be started because a required Relationship field cannot be resolved.
Model used in a Time Tracking integration must have a field of type Time Entries.
Either
Or
Collections used in a Time Tracking integration must have a field mapped to the model Time Entries field.
The selected collection does not support worklog impersonation and so has limited use as the target in a Time Tracking integration.
The worklogs will be filed under the user of the target repository connection.
Time entry filtering is configured for a collection pair but the source collection does not support it.
Artifact cannot be created currently as other potentially conflicting artifact creations are being processed. This temporary problem can occur when Tasktop Hub attempts to create artifacts on both sides of an integration concurrently.
This error will resolve itself automatically, no user action required.
The test step flow configuration is invalid.
The artifact routing for this container + work item integration is invalid because one side of the integration has multiple container collections of the same type, and artifacts are flowing away from that side.
Artifact could not be processed as it did not meet any of the configured conditions on the Shared Container Mirroring page.
Container + Work Item integrations using Shared Container Mirroring conditions require the model field within the condition to be mapped within its associated collections.
The artifact could not be processed as the artifact it depends on has not synchronized.
Container matching cannot be enabled when the parent field is mapped with an extension.
Collections with multiple artifact types cannot be used in a Container + Work Item Synchronization.
Secure password storage requires 256-bit AES encryption which is not available in the Java runtime environment.
This problem can be resolved by installing the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files in the Java runtime environment. The download is available from oracle.com including a README file with installation instructions.
Alternatively, the unencrypted level of the password store maybe used.
The connector requirements are not met.
Read the connector-specific error message to determine which requirements are unsatisfied.
To provide 3rd party components such as a library or SDK, follow the following steps:
There was an authentication error while attempting to communicate with a repository.
If these steps do not resolve the error, ensure that the user has sufficient permissions in the target repository to create and edit artifacts.
There was an authentication error with the proxy server while attempting to communicate with a repository.
If these steps do not resolve the error, contact your network administrator for assistance.
The connection settings are invalid.
If these steps do not resolve the error, contact support for additional assistance.
Tasktop Hub is unable to communicate with this repository as it is experiencing high server load. This problem is usually caused by exceeding the number of API calls a repository can receive or otherwise placing a high load on the repository.
This error will resolve itself automatically when the repository is no longer experiencing high server load. You can also set an event rate limit on the repository connection screen in Tasktop Hub to limit the number of Tasktop Hub events processed for this repository per minute.
This message is to notify you that Tasktop Hub has exceeded the allowed rate limit of the target repository. Any events that did not get processed will automatically be retried and processed upon subsequent attempts.
None.
The repository connection will be disabled until it is manually enabled.
Tasktop Hub integration services cannot be started because the current license has expired.
This problem can be resolved by installing a valid license using the following steps:
An integration cannot be run because it is configured with repository pairs which are invalid under the current license restrictions.
Perform one of the following:
A value transformation extension is present which is not permitted by the current license.
Perform one of the following:
Tasktop Hub is currently updating its operational data with a collections project replacements.
Tasktop Hub is currently updating its operational data with a collections project replacements.
A background job is currently in progress.
Wait for the background job to complete.
A background job was cancelled due to a configuration change or because Tasktop Hub was shut down.
None, the job will be resumed automatically.
Could not find a container where the target artifact could be created.
A field mapping must exist from a String or Rich Text field in the model to a Relationship or Relationships field in the target collection. Such a mapping is required to determine where to flow any commit artifacts processed by this integration.