Workflow guide
Plan an integration
Document the interface and failure behavior before connecting systems.
Confirm the enabled version and permissions in your environment. These guides do not announce a general release.
Before you start
An authorised target, working connection, a selected policy and permission to start scans. Use a test environment and a bounded budget for the first run.
Steps
- Record the environment, product version, responsible owner and permitted data. Keep credentials outside the document.
- Confirm the input/output schema, authentication, timeouts and retry ownership with the receiving system. Pin the adapter or API version used for the test.
- Exercise a missing permission and an unavailable dependency in a test environment. Ensure a retry cannot repeat a completed change.
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
For a failed scan, inspect target availability, preflight, budgets and worker state. Keep failed or skipped checks distinct from clean findings.