Managing task integration connection health
You can manage task integration connection health under Settings > Connected accounts. Each app's connection health is determined by the results of its own daily "heartbeat" API call. If the call fails, the connection to the app is broken and any associated integrations using that connection are also broken.
If an app's connection is broken, a Connection failure label appears in the Status column next to the app name in the connections list. If one or more task integrations have failed, the total displays in the Instance health column next to the red checkbox.
When you open the connection window by selecting an app, you may see 1 or 2 connections. If you see only 1 connection that indicates that you are the task integration admin and configured the integration in Hyperproof. In addition, you created an integrated task using the same set of credentials.
If you see 2 connections, the first connection is the admin connection used to configure the task integration and belongs to the administrator. If that connection isn't working, contact the administrator to fix it. The second connection is your connection, created when you configured the task.
Opening the Connected accounts window
From the left menu, select Settings.
Select Connected accounts.
Select a task integration app to view more information about its connection.
Fixing an unhealthy connection
Select the app.
The Connection window displays with a warning message about the connection failure.
Click the ... menu next to the connection and choose one of the following:
Update Credentials - Reauthenticate by entering your credentials in the popup window. You may be asked for additional information such as domain, API Key, etc.
Recheck the Connection - Review the error message in the grid. Work with your IT department to address the issue in the app itself, and then click Check now to verify that the connection is healthy.
Fixing an unhealthy task integration
A connection can be healthy, while a task that uses the connection is unhealthy. For example, you may have a Hyperproof task that generated a corresponding task in Asana, but the task no longer exists in Asana. This would cause an error with that specific task but not with the Asana itself. If you have a task in Hyperproof with a corresponding task in Jira, setting the task to Done in Hyperproof may cause incomplete Jira workflows, and trigger a Failed status until the issue is corrected in the Jira task and you have used the Sync now option to resync the tasks.
Task integration errors can typically be fixed by creating a new task or connecting the existing Hyperproof task to an existing task in the third-party app.
From the Connected accounts list, select the app with failed task integrations.
The Connection window displays with a list of tasks.
Locate the failed task and hover over the message in the Error message column to view more information about the error.
Note that there may not be any error information.
Check the task in the third-party system to make sure all requirements have been met.
In the Hyperproof Connection window Actions column, click Sync now.
If that doesn't resolve the issue, continue with the next step.
Click the task name to open the task.
Under Integrations, locate the integration name and click the Unlink icon to disconnect the Hyperproof task from the third-party task.
Select the integration again and click Attach an existing issue.
Enter the information to locate the task in the third-party system and select it.
The Review and confirm window displays and warns you that the Hyperproof task will be overwritten by the selected third-party task.
Click Confirm to continue.
Field/Option | Definition |
|---|---|
App name and account | Displays the name of the third-party app and the account name used for the selected connection. |
Admin connection | Displays the user name of the user who configured the initial integration connection under Settings > Integrations. This is an Admin connection used to set up the integration and map fields between the two systems. Click the drop-down arrow to display additional connection information:
|
My connection | Displays the user name of the user who configured the task integrations. Click the drop-down arrow to display additional connection information:
WarningIf you select Disconnect, your connection configuration is lost for all of the tasks you configured. To reconnect, you must open one of the associated tasks and reconnect it to the third-party task. This fixes all other tasks integrated with the third-party system by the same user. See Reconnecting an integration on a task. |
Tasks (..) | Displays the total number of tasks in the list, succeeded tasks. and failed tasks. |
Task name | Displays the user-specified name of the task. Click the name to open the task. |
Template | If the task was created from a repeating task, the name of the source repeating task is displayed. Click the repeating task name to open it. |
Status | Statuses include:
|
Error message | Displays any error messages generated when Hyperproof attempted to create or sync the task with the third-party system. Hover over the error message to display the entire message. |
Last checked | Date that task was last synchronized with the third-party task. |
Actions | Sync now - Click sync now to synchronize the Hyperproof task with the third-party task. |