Skip to content

When the agent gets it wrong

Most direct content writes leave no audit-log row at all, and the row a workflow write does leave carries the same user id a human edit would.

The audit log is not a record of everything an agent did. It's written only from the workflow path — submitting, approving, rejecting — and from revision approve/reject. A direct create_content, update_content, publish_content, or delete_content call never touches it. (A changeset that publishes a pending revision runs the same approve bookkeeping, and no content tool builds changesets.)

Where a row does exist, it doesn’t say "agent"

Where the workflow path does stamp an audit row, and wherever an ordinary save stamps createdBy/updatedBy, the value written is the same user id an interactive session's write would carry — an API-key-authenticated call resolves to the account that owns the key. There's no separate marker distinguishing a key-driven write from that same user editing by hand; a row that says a change came from you could just as well be an agent using your key.

Telling an agent’s writes apart from your own

The one way to make writes attributable is to give each agent its own account and its own key, named for what it is, rather than sharing your own key across every agent you run. A key is created under, and listed under, the account that owns it, so a dedicated agent account turns "who wrote this" back into a question createdBy can actually answer — a shared key can't. Nothing else in the schema will do this job for you: the audit table records a user id and an email and has no column for which key, or what kind of caller, made the change.

Undoing a bad write

Whatever the audit log does or doesn't show, Version history and rollback and Trash and permanent deletion are where you go to actually undo it — restore an earlier version onto a page an agent edited badly, or pull a deleted page back out of Trash before it's gone for good.