Pause, reconnect, or remove a base
This guide covers the supported lifecycle actions for an active Orloi base.
Orloi captures activity going forward from activation. It does not backfill Airtable history by default, including activity that happened while capture was unavailable. See Set up Orloi for the initial flow.
Change what Orloi observes
If you want to add or remove tables and fields, update the observed base's scope. The new scope applies to future activity only. Existing history in your Postgres database is not rewritten or deleted, and a scope reduction does not purge previously captured values. If you need privacy or retention cleanup, review the Advanced retention procedure.
Pause capture temporarily
If you want to stop new activity for a while, deactivate the observed base. Existing history remains available in your Postgres database. Reactivate the base when you are ready to observe again; activity from the pause is not backfilled. Verify fresh Activity before relying on reports or metrics.
Reconnect Airtable
If saved Airtable credentials are rejected, reconnect the Airtable account and verify fresh Activity after the connection is valid. A gap is not backfilled. To use a different Airtable account or base, create a new observed base; histories are not merged in place.
Stop observing permanently
If you want to stop observing a base, remove its observation configuration. Existing history in your Postgres database remains available; removing the configuration does not delete the external orloi schema or its data. Handle retention cleanup separately through the Advanced retention procedure.
If a surface is stale, treat reports, metrics, and process insights as potentially incomplete until capture is healthy. See Data lineage and freshness for stage-specific checks and incomplete-window semantics.