Common Integration Errors

This error indicates an issue with the Azure Relay.

There are relay credentials entered within the Relay Options section of the configuration of one of the Integration Connectors and that relay is turned off or not working properly.

If a relay was entered for debugging purposes, remove the credentials and click Save. Re-run the strategy.

If a relay is required for on-premises integrations, then check the server hosting the relay and make sure the relay is running and there are no error messages logged.

The integration does not have a strategy with that name.

Remove or update the schedule and pick a different strategy.

This is an error that relates to creating plans in OnePlan. The OnePlan Name field must be mapped in order to create plans in OnePlan.

Update the field mapping and map the OnePlan Name field.

There is a field name used in a filter that is not mapped. Every field used in filters must be mapped.

Update the field mapping and map the missing field(s).

This error indicates an API timeout issue. A call was made to an API and that API did not return the call within a set timeframe. In most cases, this issue is related to a single item that is being processed. If the strategy is scheduled to run again, then the item will be processed again as it is in an error state due to the timeout. If the same item fails many times, then it is possible that the specific item has a data issue. In that case review the data for that item.

This error indicates an API timeout issue. A call was made to an API and that API did not return the call within a set timeframe. In most cases, this issue is related to a single item that is being processed. If the strategy is scheduled to run again, then the item will be processed again as it is in an error state due to the timeout. If the same item fails many times, then it is possible that the specific item has a data issue. In that case review the data for that item.

This error indicates an API timeout issue. A call was made to an API and that API did not return the call within a set timeframe. In most cases, this issue is related to a single item that is being processed. If the strategy is scheduled to run again, then the item will be processed again as it is in an error state due to the timeout. If the same item fails many times, then it is possible that the specific item has a data issue. In that case review the data for that item.

This error indicates an API timeout issue. A call was made to an API and that API did not return the call within a set timeframe. In most cases, this issue is related to a single item that is being processed. If the strategy is scheduled to run again, then the item will be processed again as it is in an error state due to the timeout. If the same item fails many times, then it is possible that the specific item has a data issue. In that case review the data for that item.

Authentication Key to the OnePlan Group was deleted. Generate a new OnePlan Authentication Key and save those credentials in the OnePlan Connector.

This error can also indicate an API timeout issue. A call was made to an API and that API did not return the call within a set timeframe. In most cases, this issue is related to a single item that is being processed. If the strategy is scheduled to run again, then the item will be processed again as it is in an error state due to the timeout. If the same item fails many times, then it is possible that the specific item has a data issue. In that case review the data for that item.

This error indicates that there may be a configuration issue in OnePlan. Verify that the Microsoft Teams App is installed in OnePlan.

Asana - You do not have access to this project

In the Asana integration, if the service account does not have permissions to all projects and workspaces, then you may received this error message during processing: 

ERROR: An error occurred while retrieving sections for projects: {"errors":[{"message":"You do not have access to this project.","help":"For more information on API status codes and how to handle them, read the docs on errors: https://developers.asana.com/docs/errors"}]}

Asana - premium only

In the Asana integration, if the Asana license does not support the action that the integration is trying to perform, then an error message similar to this will be logged:

ERROR: An error occurred while creating task data: {"errors":[{"error":"premium_only_setting_task_start_date","message":"Setting start_on is not available","user_message":"Setting a start date is not allowed for this task","help":"For more information on API status codes and how to handle them, read the docs on errors: https://developers.asana.com/docs/errors"}]}

As an example, updating custom fields require premium license in Asana.