# Coverage and limitations

## Changes must emit webhooks

Tape Vault receives notifications from monitored apps. If Tape or an API caller suppresses webhooks for a change, that change may not appear in Vault.

In Tape automations, **Trigger automations** and **Trigger webhooks** are independent settings on an action. To capture a record update performed by an automation, check **Trigger webhooks** on that update action. Check subsequent update actions separately.

Turning it on affects future changes. It does not send earlier omitted notifications retrospectively.

## History is not automatically complete

Monitoring starts when the app connection is operating. The current product does not automatically backfill all earlier revisions or reconcile every notification that was suppressed or missed.

A gap in revision numbers does not by itself prove that Vault received and lost a webhook.

## Live differences and recovery have dependencies

A stored event can remain visible while its live revision difference is temporarily unavailable. Tape token permissions, content selection, the token owner's access, rate limits and Tape availability can affect live lookups and recovery.

Recovery is not guaranteed for every deleted record or field type. Some previously empty values are not restored by rollback. Native restore and recreation have different consequences; read the recovery guide before acting.

## Planned functionality

Automation-definition backups are not part of the current release. No automation-backup or automation-restore capability is promised by the current record-history features.

Last updated: 10 November 2026.