Audit Trails and Workflow History

Chase Agents maintains detailed records of all activity in your workspace. These records serve multiple purposes: debugging automation failures, demonstrating compliance, understanding team behavior, and auditing changes to automation configurations. This article describes the two primary audit surfaces: Workflow History and the Audit Log.

Workflow History

Workflow History is the run-level log for your automations. Every time an automation executes, a run record is created containing: the run start and end times, the trigger type (scheduled, webhook, manual, or event), the overall status (success, failure, or in progress), and a step-by-step breakdown of execution.

For each step in a run you can view: the step type and name, the inputs the step received, the outputs it produced, the duration it took to execute, and any error messages if it failed. This granularity makes debugging fast. When an automation fails, you do not need to guess which step caused the problem; the history shows you exactly.

Approval Step History

Runs that include a seek_human_approval_for_next_step step record additional detail: when the approval request was sent, the email address it was sent to, the timestamp of the approver's response, the decision they made (Approve or Reject), and any message they provided. This creates a time-stamped record of human decisions for compliance purposes.

The Audit Log

The Audit Log records workspace-level administrative events rather than automation run details. It captures events such as: members being invited or removed, automation configurations being created, edited, or deleted, connections being added or removed, billing changes, and workspace settings modifications. Each entry includes the timestamp, the user who performed the action, and what changed.

The Audit Log is accessible from the workspace settings panel. Only workspace admins can view audit log entries. The log is read-only and cannot be edited or deleted by workspace members. This ensures the integrity of the record.

Retention

Workflow History and Audit Log records are retained according to your plan's data retention policy. For specific retention periods, refer to your plan details or contact the Chase Agents team. Enterprise plans include extended retention and the ability to export audit data for integration with external SIEM or compliance tooling.

Using Audit Data for Compliance

For organizations with compliance requirements, the combination of Workflow History and the Audit Log provides evidence that: automated processes ran as designed and within expected parameters, human approvals were obtained before sensitive actions were taken, configuration changes were made by authorized personnel, and access to workspace resources followed expected patterns. These records can be used to support SOC 2, ISO 27001, and similar compliance reviews.

Auto-Fix Audit Trail

When the AI auto-fix engine modifies an automation step, that change is recorded in both the Workflow History for the run that triggered the fix and in the Audit Log as an automation configuration change. You can see the before and after state of the step, which model made the repair decision, and whether the repaired step succeeded. This transparency ensures that AI-driven changes to your automation logic are fully accountable.