Workflow guide

Troubleshoot a run

Isolate the failure and prepare a useful, redacted support request.

Editorial review: · Mindtro product documentation

Confirm the enabled version and permissions in your environment. These guides do not announce a general release.

Before you start

An API environment, a valid identity, a flow definition and credentials for only the providers the flow needs. Use the environment-specific OpenAPI contract.

Steps

  1. Use run, flow and correlation identifiers to distinguish input validation, model/provider, tool and worker failures. Confirm run state before retrying.
  2. Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
  3. Provide the timestamp, product/environment version, expected and observed result, and a redacted request or run identifier. Remove credentials and personal data.

Check the result

Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.

If it does not work

Use run, flow and correlation identifiers to distinguish input validation, model/provider, tool and worker failures. Confirm run state before retrying.

Contact our team →

← Pyrodit Agentic Runtime
Troubleshoot a run | Mindtro | Intelligence, Engineered