Configured connection or verified live feed?

Separate configuration from evidence

A connection record can describe a provider, environment and the existence of a managed secret reference. Those details help organize implementation. They do not prove that access works, data is current or a business workflow has completed.

1. Check the provider and selected environment.
2. Look for the relevant verification evidence and time.
3. Confirm that the actual handoff and expected record were tested.

• Orchesphere currently stores connection configuration; it does not verify a live feed through an unprovisioned execution environment.
• A secret reference is not a credential to copy into a message.

Check the claim being made

A successful authentication check, a readable report and a completed business transaction establish different things. Verification should match the intended use of the connection and the permissions involved.

• What operation was tested?
• Which environment and record were used?
• When was the result obtained, and who reviewed it?

When a connection appears unavailable

Record the visible status and the workflow affected. Ask the responsible owner to distinguish configuration, permission, provider and data issues before retrying actions.

• The provider, environment and affected workflow.
• The last verified result, if one exists.
• A redacted error and a safe record reference through the agreed private channel.