Some integrations require a specific configuration that requires regular updates. This is the case, among others, for integrations using a Personal Access Token (e.g. Azure DevOps). If an integration does not synchronize data to Axify, an error message will be displayed in the concerned axis.
Here are some troubleshooting steps to restore data synchronization.
Unlink and link the affected integration
This is the first step to try. Since Axify is constantly evolving, though we do our due diligence to prevent this, it is possible that an update affects a particular axis or integration.
So, by unlinking the integration and then linking it again, you are assured of using the most recent configuration. Rest assured, our integrations synchronize data retroactively (except the webhooks feeding the DORA metrics), so you won't lose track of your project's variations.
Psst! Yes, we are all familiar with the phrase "Have you tried turning off and on again".
Check the settings at the source
- Is the data you want to synchronize in the right format?
- When synchronizing a project board, it is advisable to check the configuration of your board at the source to ensure that the right data will be synchronized to Axify in the desired format.
- For example, synchronizing project data for a specific item type requires the creation of an independent board on which a filter (or query) has been applied in order to isolate the desired item type. This board can then be linked to Axify to synchronize the desired data.
You can also check out this help article for more information on optimizing data synchronization.
- Is the data to be synchronized included in your filters (query) at the source?
- In the same spirit as the format mentioned in the previous point, we recommend that you check your filters (or queries) at the source to ensure that there are no data exclusions. Axify uses various information to populate the available metrics including the type of item, but also their status. Therefore, if your filter or query excludes items with the status "Resolved", you will not have access to some metrics such as cycle time distribution, expected service level, or throughput.
- In the same spirit as the format mentioned in the previous point, we recommend that you check your filters (or queries) at the source to ensure that there are no data exclusions. Axify uses various information to populate the available metrics including the type of item, but also their status. Therefore, if your filter or query excludes items with the status "Resolved", you will not have access to some metrics such as cycle time distribution, expected service level, or throughput.
- Does your integration require a special configuration or an expired personal access token (PAT)?
- If so, unlink the integration, generate a new PAT at the source, and then link the integration back to the newly generated PAT. For your information, it is generally recommended to select the longest validity period, such as one year, to limit the frequency of PAT updates. Also, be sure to add a reminder to your calendar or your team's calendar to be notified of the next required update.
- If so, unlink the integration, generate a new PAT at the source, and then link the integration back to the newly generated PAT. For your information, it is generally recommended to select the longest validity period, such as one year, to limit the frequency of PAT updates. Also, be sure to add a reminder to your calendar or your team's calendar to be notified of the next required update.
- In the case of DORA metrics; are your deployments triggering Deployment Events that Axify can count?
- If not, we advise you to check your deployment flow and potentially update it so that a Deployment Event matching the criteria described in our article on webhooks configuration is generated. Axify will then be able to intercept and compile your deployments.
- If so and data still doesn't show up in Axify, make sure your deployment environments are properly configured in your project settings.
Your data is still not synchronizing?
Contact us by submitting an assistance request! We'll be happy to help you get your data back in sync.