Rollback

Every automation carries a question in the back of your mind: what if it does something wrong? On etg24, the answer is a recovery workflow — not a support ticket.

The recovery workflow

1. Spot the problem — or be told about it.
2. Find the change in the change log: which agent, which entity, which fields, when.
3. Disable the key if the agent is misbehaving — instantly, everywhere it was active.
4. Roll back the data. Because deletes are soft deletes almost everywhere, the removed data still exists and can be restored.

Why this works

Rollback is only possible because the other concepts are in place:

• Change attribution makes the bad action findable and attributable.
• Soft delete keeps the data restorable.
• Per-agent attribution and scopes keep the blast radius small — one disabled key, one scoped mistake, not a full shutdown.

An agent that deletes the wrong contact, object or document is identified in the log, stopped, and undone. That is the safety story behind the whole platform.