This article explains why a connection may say it is failing when it is tested, despite the connection still working in active Okta Workflows.

• Okta Workflows

The process that checks a particular connection's health inside Okta Workflows is simply an API call from which we expect a successful response. If the health check starts failing, there can be cases where the connection will still work. The most likely explanations in these scenarios are as follows:

• Something about the service's API changed that broke our connection health check.

• An intermittent error that will resolve itself over time (this could be an issue with the service's API uptime, for example).

If the workflow is still successfully executing through actions using that connection, then it's just an issue with the health check. If the connector's actions fail, it is an issue with the entire connection.