Connection to an application failed

When APIcenter can no longer log in to an application, processing stops for that application. The activity then shows a message about authentication, authorization or a token. When logging in fails repeatedly, the dashboard shows Connection to and the name of the application, followed by failed.

Why it happens

Usually the login at the application changed or expired, for example:

• the password or API key was changed in the application itself;
• the access of APIcenter was revoked or expired;
• the user you connected with got fewer rights or no longer exists.

What APIcenter does by itself

• When the login fails, APIcenter stops the application and the flow, so new errors do not keep appearing.
• APIcenter retries the records that were not processed because of this automatically: four times, the last time about 12.5 hours after the first error.
• APIcenter regularly tries to log in again by itself, and renews the access where it can. When that works, it switches the application and the flows it stopped back on.
• When that fails three times, the problem appears on the dashboard. Then you need to act.

How to solve it

1. On the dashboard, click Reconnect next to the problem, or go to Applications and open the application.
2. Enter the new details and click Save, or click Authorize and log in to the application again.
3. Click Test Connection. "Connection is good!" means the connection works again.
4. Open the flows of the integration. If one still shows Flow is stopped, click Resume Flow.

Read more about this page in Editing an application. Which details an application needs is in the manual of that application.

Tips

• Changed a password or key in the application itself? Change it in APIcenter right away too.
• Does Test Connection show a Test Connection Error? Read the message in the box. Click Ask the AI assistant for an explanation.