Error Message Appendix

Description

An unexpected error has occurred.

User Action

Attempt to resolve error according to the specific error message.

Description

The maximum number of allowable errors has been reached. Any errors encountered after the maximum number will be discarded.

User Action

1. Open the errors page and resolve the listed errors

Description

The system has run out of memory. Services have been stopped.

User Action

1. Increase the amount of memory available (see help docs).
2. Restart Tasktop Hub.

Description

The artifact association could not be imported as an existing artifact association conflicts with it.

User Action

Contact support for assistance.

Description

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.

User Action

None, data migration will be resumed automatically.

Description

Migration cannot be completed as there are errors related to disabled repositories.

User Action

1. Open the Activity page and delete all errors related to the specified repository, or
2. Navigate to the Repositories page and enable the specified repository

Description

There was a network error when attempting to communicate with a repository.

User Action

1. Check the network connection between Tasktop Hub and the repository.
2. Try connecting again later.

If the problem persists, contact your network administrator.

Description

An unexpected connector exception has occurred.

User Action

Attempt to resolve error according to the specific error message.

Description

An exception has occurred during the execution of a connector operation.

User Action

Attempt to resolve error according to the specific error message.

Description

An unexpected error has occurred while attempting to establish a connection with an LDAP directory.

User Action

Attempt to resolve error according to the specific error message.

Description

An unexpected error has occurred while communicating with an LDAP directory.

User Action

Attempt to resolve error according to the specific error message.

Description

The authentication state for a repository connection has expired.

User Action

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.

Description

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.

User Action

1. Determine the cause of the problem from the specific error message
2. Navigate to the referenced repository collection or artifact union
3. Correct the problem on the repository and then click Refresh Projects, or
4. Remove the referenced project from the repository collection or artifact union
5. If a project has been renamed add the renamed project back
6. Ensure all related routing, filtering, and mapping configurations are valid and up to date

Description

There was an unexpected error while attempting to authenticate with a repository.

User Action

Attempt to resolve error according to the specific error message.

Description

The project configuration is outdated.

User Action

1. Identify the outdated project configured from the specific error message
2. Remove the outdated project from the associated Repository Collection or Artifact Union
3. Select Manage Projects and press the Refresh button
4. Add the project back

Description

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.

User Action

1. Go to the affected repository collection configuration page
2. If the project has been deleted, remove the referenced project from the repository collection
3. If the project has been moved, click  Manage Invalid Projects and select the projects replacement
4. Ensure all related routing, filtering, and mapping configurations are valid and up to date

Description

The high-level container (i.e. the type of container chosen when clicking  Manage Projects on the Collections screen) has changed.

User Action

Before resolving this issue, please:

1. Review and write down the current artifact routing configuration for any integrations utilizing this collection as these must be reconfigured once the issue is resolved.
2. To ensure you understand the changes made to your collection, please navigate to the collection and review what is now selected under  Manage Projects. No changes will need to be made on this screen.

Once this issue is resolved, your artifact routing will be removed from any relevant integrations, and need to be manually reconfigured.

Description

The artifact is locked by another user or process.

User Action

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.

Description

The repository connection could not be established due to an insecure connection.

User Action

• Attempt to resolve error according to the specific error message, or
• Navigate to the specific Repository and enable the setting for allowing insecure connections

Description

The artifact union configuration is invalid.

User Action

1. Navigate to the artifact union configuration screen,
2. Correct the invalid configuration according to the specific error message

Description

The events processing for this repository may be delayed because the repositorys event rate limit is set too low.

User Action

1. Navigate to each integration utilizing this repository and update the change detection interval, or
2. Navigate to the repository connection screen and update the event rate limit.

Description

The repository query could not be created.

User Action

1. Verify that the query has not been renamed or deleted on the repository
2. Ensure that the repository user has sufficient permissions to access the query

Description

An integration must contain at least one route.

User Action

1. Navigate to the integration routing page
2. Add at least one route

Description

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.

User Action

1. Navigate to the integration page
2. Adjust the configuration to be valid (according to the messages)
3. If this integration was created via the web UI, consider contacting support

Description

Collections used in an integration must all be attached to the same model.

User Action

1. Determine which model the integration should be using
2. Navigate to the integration and determine which collections are not using this model
3. Either remove the identified collections from the integration, or
4. For each identified collection, set the mapping to the correct model

Description

Repository Collections used in an integration must have a mapping to a model.

User Action

1. Navigate to the collection
2. Select a Model to create a mapping

Description

An integration must have a source collection.

User Action

1. Navigate to the Integration
2. Add a collection to be used as a source

Description

An integration must have a target collection.

User Action

1. Navigate to the Integration
2. Add a collection to be used as a source

Description

An integration failed to locate the artifact to be modified. This can be caused by:

• a missing formatted ID value on the source artifact,
• an invalid formatted ID value on the source artifact, or
• the absence of a target collection which contains an artifact matched by the formatted ID.

See the detailed message for more details about the parts of the lookup that failed.

User Action

1. Navigate to the integration page
2. Ensure the key field is configured correctly on the field flow page
3. Ensure the data on the source artifact is correct
4. Ensure a matching artifact is contained in a target collection

Description

The filter used in the integration has become invalid.

User Action

1. Navigate to the integration filter in error.
2. Resolve each error that appears in the filter.

Description

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.

User Action

1. Navigate to the integration page
2. Select the two collections missing a key identifier
3. Navigate to the field flow page and configure a key identifier

Description

All specified routes of an integration must be configured.

User Action

1. Navigate to the integration routing page
2. Configure all routes which require configuration

Description

The conditional routing configuration of the integration has become invalid.

User Action

1. Navigate to the integration route in error.
2. Resolve each error that appears in the routing configuration.

Description

The repository query used in the collection has become invalid.

User Action

1. Navigate to the collection.
2. Resolve the error by selecting a different repository query.

Description

Tasktop Hub is currently updating its operational data for an integration.

User Action

1. Wait for the data to be updated.

Description

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).

User Action

1. Navigate to each collection participating in the integration to review what is now selected under 'Manage Projects.'
2. Navigate to each integration and reconfigure the artifact routing. Once the routing is valid, this issue will clear.

Description

The twinless artifact update for this integration is invalid.

User Action

1. Navigate to the twinless update configuration for this integration.
2. Resolve the error according to the specific error message.

Description

An Enterprise Data Stream Integration must reference a single SQL collection.

User Action

• Select a SQL Collection for the target of the Integration that is in error.

Description

An Enterprise Data Stream Integration must reference at least one Collection to be used as a source of artifacts.

User Action

Select a source Collection for the Integration that is in error.

Description

An Enterprise Data Stream Integrations data Collection must be mapped to a model. This corresponds to the model desired to be reported on.

User Action

Add mappings for the Collection used in the Enterprise Data Stream Integration.

1. navigate to the Collection
2. add a mapping to a model

Description

An Enterprise Data Stream Integration source Collection must be mapped to the same model as the target Collection.

User Action

Add relationship to the model for the source Collection used in the Enterprise Data Stream Integration

1. navigate to the Integration
2. identify the model of the target Collection
3. navigate to the source Collection in error, and ensure that its model matches the model of the target Collection
   • if the source collection is a Repository Collection, add a mapping to the corresponding model
   • if the source collection is a Gateway Collection, ensure its model is set to the corresponding model

Description

An Enterprise Data Stream Integrations Collection must have exactly one project.

User Action

1. Navigate to the Collection
2. Ensure it has exactly one project which corresponds to the database table

Description

An Enterprise Data Stream SQL Collections underlying database table is missing a required column.

User Action

Add the required column to the underlying database table. See error message for missing column id.

Description

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.

User Action

This problem can be resolved by installing a valid license using the following steps:

1. Obtain a valid license by contacting the Tasktop Support Center
2. Navigate to the settings page
3. Press the Apply New License button under License
4. Paste in the license text and press Save

Description

The repository connection cannot be used because connections to repositories of this type are not enabled by the license.

User Action

This problem can be resolved by installing a valid license using the following steps:

1. Obtain a valid license by contacting the Tasktop Support Center
2. Navigate to the settings page
3. Press the Edit button under License
4. Paste in the license text and press Save

Description

The integration cannot be used because conditional field flow configurations exist in this integration but are not enabled by the license.

User Action

Perform one of the following:

• Remove the conditional field flow from the integration
• Contact the Tasktop Support Center to obtain and install a license that includes the conditional field flow feature

Description

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.

User Action

Perform one of the following:

• Remove the mappings using a field from an artifact union from the collection
• Contact the Tasktop Support Center to obtain and install a license that includes the artifact union feature

Description

Tasktop Hub integration services cannot be started because secure password storage has not been configured and initialized.

User Action

1. Navigate to the Settings page
2. Specify the Master Password under Secure Password Storage

Description

The Tasktop Hub services restart is taking longer than expected.

User Action

• Wait for the Tasktop Hub services to restart and this issue will be removed automatically.
• If the Tasktop Hub services do not restart (this issue is still present) after 30 minutes, please contact the Tasktop Support Center for assistance:  https://links.tasktop.com/support.
• Do not restart Tasktop Hub without assistance from support

Description

The mapping cannot be applied since the mapping is not valid for the artifacts in the current context.

User Action

1. Determine the source of the problem from the specific error message
2. Either update the mapping to match the artifacts and model in use, or
3. Update the corresponding artifact schema to match the mapping, for example by changing a field type

Description

The collection model mapping is not valid due to inconsistencies between the collection schema, the model schema and the mapping.

User Action

1. Determine the cause of the problem from the specific error message
2. Navigate to the mapping
3. Update the mapping to match the collection and model in use, or
4. Update the corresponding collection artifact schema to match the mapping, for example by changing a field type, or
5. Update the model to match the mapping, for example by adding a field, or changing a field type

Description

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.

User Action

1. Identify the fields and values that are in error from the specific error message
2. Correct the source data, either by
   • updating the source artifact, or
   • by making changes to the mapping, or
   • by making changes to the target system so that the provided data is valid, or
   • by providing a new artifact via a Gateway Collection

Description

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.

User Action

This error will resolve itself automatically, no user action required.

Description

The field flow configuration is not valid due to inconsistencies between the the model schema and the field flow.

User Action

1. Determine the cause of the problem from the specific error message
2. Navigate to the integration
3. Select the collection pair
4. Navigate to the field flow
5. Update the field flow to match the model in use, or
6. Update the model to match the field flow, for example by adding a field

Description

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.

User Action

1. Determine the cause from the specific error message
2. Either retry the corresponding activity, or
3. Verify the state of the created artifact and manually adjust values as necessary

Description

The conflict resolution strategy configuration is invalid.

User Action

1. From the integration, navigate to the conflict resolution strategy
2. Select an option for the conflict resolution strategy

Description

Artifact could not be processed as it did not meet any of the configured conditions on the Conditional Artifact Routing page.

User Action

• Update the conditions configured on the Conditional Artifact Routing page to ensure the artifacts field value is accounted for, or
• Update fields on the artifact to ensure that it meets the conditions set on the Conditional Artifact Routing page, or
• Update specification for handling artifacts not matched by conditions configured on the Conditional Artifact Routing page to  Ignore or  Default Route instead of  Error.

Description

An extension provided invalid values when attempting to transition an artifact.

User Action

1. Identify the extension that produced invalid values
2. Identify the fields and values that are in error from the specific error message
3. Modify the extension to produce a valid transition

Description

An extension attempted to transition an artifact with the same transition more than once.

User Action

1. Identify the extension from the error message
2. Modify the extension to avoid repeated transitions of the same type for an artifact

Description

An extension completed with an error. See the specific error message for details.

Extensions complete with errors for one of two reasons:

• the extension intentionally raised an error, for example to indicate that a business rule was not satisfied
• the extension itself has an error in its implementation

User Action

1. Determine from the specific error message the cause of the error
2. Either modify the extension to prevent the error from occurring, or
3. Modify the source or target artifact to satisfy the condition that caused the error

Description

A state transition extension is configured in a collection that has no model fields selected.

User Action

Either disable the state transition of the collection or select model fields for the state transition.

To select the fields for the state transition:

1. navigate to the collection
2. navigate to the collection state transitions via the  Configure State Transition link
3. add the model fields required by the state transition in "State Transition Fields"

To disable state transitions in the collection:

1. navigate to the collection
2. navigate to the collection state transitions via the  Configure State Transition link
3. select  None for "State Transition"

Description

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.

User Action

• None; wait for the error to be resolved automatically, or
• Remove the unresolved link from the artifact being synchronized

Description

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.

User Action

• Remove the link from A to B, or
• Use the Artifact Pairs tab on the Activity page to delete any invalid or outdated associations involving B, or
• Remove any unnecessary synchronization integrations which can affect B

Description

An unexpected error occurred when creating the artifact. The artifact may or may not have been created.

User Action

1. Do not retry the event without guidance from Tasktop Support,
2. Contact the Tasktop Support Center for assistance: "https://links.tasktop.com/support"

Description

The repository does not support artifact creation.

User Action

1. Navigate to the corresponding integration,
2. Disable artifact creation flow into the specified collection,
3. Remove all routes flowing into the specified collection.

Description

A state transition extension is configured in a collection that requires fields that are not configured in the model.

User Action

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:

1. navigate to the model
2. add the fields

To change the required fields of the state transition extension from the collection:

1. navigate to the collection
2. navigate to the collection state transitions via the  Edit state transition link
3. modify the list of model fields

Description

The work item artifact could not be synchronized due to a missing or invalid route.

User Action

1. Verify which container this artifact is in in the repository, and ensure that either that container or one of its ancestors has been configured as part of a mirrored container structure; or
2. Ensure that a route has been created for the container in which this artifact originates in the work item integration; or
3. Ensure that the target container has not been deleted. If it has, and if an error exists for it, re-create the container on the Errors screen. To ensure you see an error for the deleted container, make a change to the still-existing corresponding container in the other collection.

Description

The artifact could not be synchronized because the target container could not be found.

User Action

1. No action needed, the synchronization should be fixed automatically when the containers synchronize.

Description

A transition was attempted on an artifact but an error resulted.
The artifact may be in an incorrect state.

User Action

Either address the cause from the specific error message, or disable/reconfigure the state transition of the collection.

1. If the specific error message has a cause, verify the state of the target artifact and manually adjust values as necessary

To disable/reconfigure state transitions in the collection:

1. navigate to the collection
2. navigate to the collection state transitions via the  Configure state transition link
3. adjust the relevant state transitions

Description

The container associated with the parent container of this artifact could not be found.

User Action

• If the parent container is configured in a route, update the routing configuration to use an existing container
• If the parent container is synchronized by an integration, update the parent container to generate an event for the parent container, and use the  Recreate Artifact action

Description

For the artifact pair import to succeed, the associated integration must be running.

User Action

• Run the integration associated with the artifact pair file.

Description

An error occurred when processing the output of an extension. See the specific error message for details.

User Action

1. Determine from the specific error message the cause of the error
2. Either modify the extension to prevent the error from occurring, or
3. Modify the source or target artifact to satisfy the condition that caused the error

Description

Field value configuration required. The field type for a field in your integration has changed and its field values must be re-mapped.

User Action

1. Navigate to the appropriate collection (linked above)
2. Go to Field Mapping screen
3. Click  Configure next to any fields with a  ! icon
4. Map the field values and save
5. Important: Remove this issue to re-enable the integration

Description

The comment flow configuration is not valid. This can happen if a repositorys comment visibility support has changed.

User Action

1. From the integration, navigate to the comment flow
2. Configure the comment flow as desired

Description

The Conditional Field Flow configuration is not valid. This can happen if either a field or value is not resolvable in the model schema.

User Action

1. From the integration, navigate to the Field Flow
2. Configure the Conditional Field Flow so that all fields and values configured in the conditions are in the respective model used.

Description

The test step model mapping is not valid due to inconsistencies between the test step schema, the test step model schema and the mapping.

User Action

1. Determine the cause of the problem from the specific error message
2. Navigate to the test step mapping
3. Update the mapping to match the collection and model in use, or
4. Update the corresponding test step schema to match the mapping, for example by changing a field type, or
5. Update the test step model to match the mapping, for example by adding a field, or changing a field type

Description

The time entry model mapping is not valid due to inconsistencies between the time entry schema, the time entry model schema and the mapping.

User Action

1. Determine the cause of the problem from the specific error message
2. Navigate to the time entry mapping
3. Update the mapping to match the collection and model in use, or
4. Update the corresponding time entry schema to match the mapping, for example by changing a field type, or
5. Update the time entry model to match the mapping, for example by adding a field, or changing a field type

Description

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.

User Action

The configuration delta table migration will complete as a background job, no user action required.

Description

Failed to transform imported configuration change into change applicable for this instance due to missing elements.

User Action

Create the required missing elements before re-importing the configuration change.

Description

A Gateway Collection has been used, but the collection is not configured as a source in an integration. The payload has been lost.

User Action

1. Use the Gateway Collection in an integration, or
2. Stop pushing to the collection (from the external source)

Description

A Gateway Collection must configure the Relationship(s) fields to associate them with the repository having referenced artifacts.

User Action

1. Navigate to the Gateway collection
2. Locate the  Relationship Field Configuration section in the UI
3. For each field, select the repository that is associated with that relationship.

Description

A Gateway Collection must have a model configured.

User Action

1. Navigate to the Gateway collection
2. Select a model and save the changes

Description

A gateway collection has been configured with a payload transformation extension, which is not permitted by the current license.

User Action

Perform one of the following:

• Delete the offending gateway collection
• Remove the payload transformation extension from the offending gateway collection

Description

A Gateway Collection must use a token.

User Action

1. Navigate to the Gateway collection
2. Generate a token and save the changes

Description

An error occurred while attempting to send an email.

User Action

1. Verify that the email settings are specified correctly in the settings
2. Attempt to resolve error according to the specific error message

Description

The mail server rejected the client connection because it was not able to authenticate.

User Action

1. Verify that the email settings are specified correctly in the settings
   • Double-check the email server hostname and port
   • Double-check the email server credentials
2. Attempt to resolve error according to the specific error message

Description

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.

User Action

Do not cancel this error or run the associated integration without consulting Tasktop Support. (https://links.tasktop.com/support)

Description

An unexpected error has occurred. Check the specific error message for details.

User Action

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.

Description

The entity was not found because the entity no longer exists on the server.

User Action

Ensure that the provided entity id is correct, and if not correct the id and try again.

Description

The data provided was not valid. See the specific error message for details.

User Action

Correct the problem described in the specific error message and try again.

Description

The connector kind was not found.

User Action

Ensure that the connector kind is specified correctly and try again.

Description

The request entity was not valid JSON.

User Action

Ensure that the request payload is formatted as a valid JSON entity and try again.

Description

Secure password storage has not been initialized.

User Action

Configure secure password storage via the settings page.

Description

Error connecting to repository. See the specific error message for details.

User Action

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.

Description

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.

User Action

1. Verify that the temporary directory of the Tasktop Hub application is writable,
   • The Tasktop Hub application must have write permissions to the directory
   • The directory must have sufficient available space
2. Try again

Description

Tasktop Hub has been stopped due to unrecoverable errors. See error log for more details.

User Action

Correct the problem described in the specific error message and restart.

Description

The configuration database is unavailable.

User Action

Ensure the configuration database is online and can be reached and ensure Tasktop Hubs database settings are correct.

Description

The provided connection settings are not valid. See the specific error message for details.

User Action

Correct the problem described in the specific error message and try again.

Description

The configuration database is locked for maintenance and cannot be used.

User Action

Wait for the ongoing maintenance to complete.

Description

The Configuration database is in use by another instance of the application.

User Action

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.

Description

Temporary error connecting to repository. See the specific error message for details.

User Action

Retry your action. If the problem persists, contact your administrator for assistance.

Description

The repository connection could not be established due to an insecure connection.

User Action

• Attempt to resolve error according to the specific error message, or
• Navigate to the specific Repository and enable the setting for allowing insecure connections
• For Tasktop Hub Cloud, refer to the User Guide for more information on resolving this error.

Description

Configuration applicable to the current deployment is incomplete or invalid.

User Action

Contact Tasktop customer support.

Description

The current user is not authorized due to a restriction in the license.

User Action

Contact your Tasktop Hub administrator.

Description

Tasktop integration services cannot be started because the current license has expired.

Description

Tasktop integration services cannot be started because the no license has been configured.

Description

The application is starting up and cannot be accessed at this time.

User Action

Wait for the application to finish starting up

Description

The connection settings for the operational database are inaccessible.

User Action

Ensure the tasktop-db.json file is correctly formatted and the Tasktop Hub user has permission to read it.

Description

The history page is not available before the necessary data migrations are complete.

User Action

Wait for the migrations to complete.

Description

The repository connection will be disabled until it is manually enabled.

User Action

• Enable the repository connection manually on the Repository Connection page, or
• Leave the repository connection disabled and ignore this warning

Description

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.

User Action

• Use the  Recreate Artifact action to have Tasktop Hub recreate the artifact that was deleted in the end system and associate it with the still-existing artifact in the other repository (putting them in sync with one another), or
• Delete the associated artifact, or
• Move the associated artifact out of its collection such that the artifact is no longer synchronized, or
• Apply an artifact filter to ensure updates to the artifact will not be synchronized. To do so, make sure the artifact does not meet the filter criteria specified and make sure to configure the filter to apply to artifact updates

Description

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.

User Action

• Change the conflict resolution strategy to have one of the repositories dominate in case of a conflict, or
• Manually change the conflicting value on at least one of the artifacts such that there is no longer a conflict, or
• Change the field flow of the affected field to be unidirectional (in which case a conflict is not possible)

Description

A conflict was detected when synchronizing artifact containment. A conflict occurs when one or more containers of synchronized artifacts is changed for both artifacts.

User Action

• Change the container of one or both artifacts to its original value or
• Change the conflict resolution strategy to have one of the repositories dominate

Description

Unable to find a new value for an unchanged dependent field.

User Action

• From the error message find the field that the field in error depends on
• In the repository add a value with the same label as the one provided in the error message

OR

• Change the field that the field in error depends on back to its original value

OR

• Remove the mapping for the field that the field in error depends on

Description

Multiple matching containers were found when attempting to match containers.

User Action

• Disable container matching in the container mirroring configuration, or
• Rename the containers such that only one container matches, or
• Change the container matching configuration to choose the first matching container, or
• Change the container matching configuration to match containers differently

Description

The integration cannot be started because a required Relationship field cannot be resolved.

User Action

• Create an integration to synchronize the artifacts referenced by the specified field, or
• Add a constant mapping to the specified field.

Description

Model used in a Time Tracking integration must have a field of type Time Entries.

User Action

Either

1. Navigate to the model
2. Add a field of type Time Entries

Or

1. Create or select another model having a field of type Time Entries
2. Ensure that each collection used in the integration is using the selected model

Description

Collections used in a Time Tracking integration must have a field mapped to the model Time Entries field.

User Action

1. Navigate to the collection model mapping
2. Add a field mapping to the model Time Entries field

Description

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.

Description

Time entry filtering is configured for a collection pair but the source collection does not support it.

User Action

1. Navigate to the integration
2. Select the collection pair
3. Navigate to Time Entry Filtering
4. Disable the filter

Description

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.

User Action

This error will resolve itself automatically, no user action required.

Description

The test step flow configuration is invalid.

User Action

1. Navigate to the test step flow configuration screen,
2. Correct the invalid flow configuration according to the specific error message

Description

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.

User Action

1. Navigate to each integration and reconfigure the artifact routing. Once the routing is valid, this issue will clear.
2. When multiple container collections of the same type exist, integrations can only routed toward that side of the integration.
3. Ensure artifact flow is not bidirectional.

Description

Artifact could not be processed as it did not meet any of the configured conditions on the Shared Container Mirroring page.

User Action

• Update the conditions configured on the Shared Container Mirroring page to ensure the artifacts field value is accounted for, or
• Update fields on the artifact to ensure that it meets the conditions set on the Shared Container Mirroring page, or
• Update specification for handling artifacts not matched by conditions configured on the Shared Container Mirroring page to  Ignore or  Default Type instead of  Error.

Description

Container + Work Item integrations using Shared Container Mirroring conditions require the model field within the condition to be mapped within its associated collections.

User Action

1. Navigate to the associated collections,
2. Add a field mapping to and from the model field used within the Shared Container Mirroring conditions

Description

The artifact could not be processed as the artifact it depends on has not synchronized.

User Action

• Ensure that the artifact specified within the detailed error message is included in the integration,
• Wait for it to synchronize

Description

Container matching cannot be enabled when the parent field is mapped with an extension.

User Action

• Remove the extension from the parent field mapping within the related collections, or
• Disable container matching in the related integration

Description

Collections with multiple artifact types cannot be used in a Container + Work Item Synchronization.

User Action

1. Use a different collection in the integration
2. Remove unnecessary artifact types from the collection

Description

Secure password storage requires 256-bit AES encryption which is not available in the Java runtime environment.

User Action

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.

Description

The connector requirements are not met.

User Action

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:

1. Navigate to the  Repositories screen.
2. Select the repository for which the requirements were unsatisfied.
3. On the repository connection screen, provide the required files.

Description

There was an authentication error while attempting to communicate with a repository.

User Action

1. Verify that the credentials for the associated repository are correct in the settings.

If these steps do not resolve the error, ensure that the user has sufficient permissions in the target repository to create and edit artifacts.

Description

There was an authentication error with the proxy server while attempting to communicate with a repository.

User Action

1. Verify that the proxy credentials for the associated repository are correct in the settings.

If these steps do not resolve the error, contact your network administrator for assistance.

Description

The connection settings are invalid.

User Action

1. Open the connection settings page for the repository that is in error.
2. Update the connections settings to valid values.

If these steps do not resolve the error, contact support for additional assistance.

Description

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.

User Action

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.

Description

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.

User Action

None.

Description

The repository connection will be disabled until it is manually enabled.

User Action

• Enable the repository connection manually on the Repository Connection page, or
• Leave the repository connection disabled and ignore this warning

Description

Tasktop Hub integration services cannot be started because the current license has expired.

User Action

This problem can be resolved by installing a valid license using the following steps:

1. Obtain a valid license by contacting the Tasktop Support Center
2. Navigate to the settings page
3. Press the Apply New License button under License
4. Paste in the license text and press Save

Description

An integration cannot be run because it is configured with repository pairs which are invalid under the current license restrictions.

User Action

Perform one of the following:

• Delete the offending integration
• Disable the offending integration
• Update the offending integration to use repository pairs allowed under the current license restrictions

Description

A value transformation extension is present which is not permitted by the current license.

User Action

Perform one of the following:

• Provide a license that includes extensions of this type, or
• Remove extension by navigating to the the Settings -> Extensions page

Description

Tasktop Hub is currently updating its operational data with a collections project replacements.

User Action

1. Wait for collection update to complete.

Description

Tasktop Hub is currently updating its operational data with a collections project replacements.

User Action

1. Wait for collection update to complete.

Description

A background job is currently in progress.

User Action

Wait for the background job to complete.

Description

A background job was cancelled due to a configuration change or because Tasktop Hub was shut down.

User Action

None, the job will be resumed automatically.

Description

Could not find a container where the target artifact could be created.

User Action

1. Identify the target repository where the container could not be located for the target artifact from the specific error message.
2. Ensure a container that satisfies the following constraints is created in the target repository:
   • Is able to contain the target artifact.
   • Is a sibling of the container of the referenced artifact.

Description

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.

User Action

1. Configure a field mapping from your model Commit Message field to a Relationship or Relationships field in the target collection.