Investigate cost spike
Investigate a sudden increase in AI spend.
Investigate a sudden increase in AI spend.
## Before you start
- Confirm the target workspace. - Confirm your role and plan access. - Use non-sensitive test data first. - Preserve request IDs, trace IDs and timestamps while testing.
## Steps
- 1. Open the relevant Kadryn page.
- Confirm permissions and workspace context.
- Apply the smallest safe change.
- Run a non-sensitive test.
- Verify the result in Logs & Traces, Costs, Alerts or Guardrails.
- Document the production owner and rollback path.
## Verify
- The expected item appears in the matching Kadryn menu. - Logs & Traces contains enough evidence to debug the workflow. - Costs, Alerts or Guardrails reflect the expected state. - No secret is present in logs, screenshots or payload metadata.
## Production notes
- Roll out gradually when the workflow can affect production traffic. - Use idempotency for retryable writes. - Keep a rollback path for configuration changes. - Document who owns the integration or workflow.
## Related pages