Workflow guide
Check access and controls
Test the intended access boundary before broadening use.
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
- Scope tool capabilities and budgets to the agent. Keep secrets in deployment configuration; do not insert them into prompts or exported traces.
- Test both an allowed action and an action outside the assigned scope. Review access again when the user, source or policy changes.
- Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
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.