An environment may appear disconnected when FlowKeyOps cannot confirm authorized communication with its automation destination.
Check the scope
Determine whether one environment or every environment is affected. Note the last connected time and any recent network, certificate, endpoint, credential, or permission changes.
Review safe connection details
- The selected workspace and environment
- The endpoint hostname and protocol, without embedded credentials
- The authorization or connection status
- The last successful check and current error reference
- Whether the automation runtime itself is available
Check the destination
Confirm the runtime is running and reachable through the intended network path. Check certificate validity, firewall or access-policy changes, and whether the integration identity remains authorized. Do not make the runtime public or disable certificate verification as a workaround.
Retry carefully
After correcting the cause, use the supported connection check once and allow it to complete. Repeated retries can obscure the timeline or trigger protective limits.
Escalate with context
Provide the environment identifier, endpoint hostname, last-connected time, error reference, and recent changes. Do not send the integration token, private key, or full authorization header.