Connection
Connection identity and Environment values are shared platform concepts, but creation, assignment, and execution placement differ by runtime. Choose the article that matches your Workflow:
The shared Connections screen lists and organizes Connections from both runtimes.
Automatic health checks
Flowgear periodically tests saved Connection values in their configured Environments when the Node supports Connection testing. This applies to v1 Runtime and v2 Runtime Connections. The test runs through the appropriate runtime host; for a v2 Runtime Connection, its saved Cluster selection determines where the test runs.
A successful test establishes that the Node's Connection test completed successfully at that time. It does not prove that every operation, permission, or business record needed by a Workflow is available. For example, a test that reads account information does not establish permission to create an invoice.
Health results are recorded separately for each Environment:
| Result | Meaning |
|---|---|
Success |
The most recent completed test succeeded. |
Failed |
The most recent completed test failed. Review its message, credentials, access, and runtime host availability. |
Unsupported |
The Node does not provide a Connection test. This does not mean its credentials are invalid. |
Unknown or no recorded result |
A completed health check has not established a result. Absence of a result is not a failed test. |
The record includes the last test completion time and, when available, the last successful test time. A later failure does not erase the earlier success time. These are periodic checks, so use a manual Connection test and a representative Workflow run when validating a change immediately. Automatic testing has no per-Connection schedule control.