Table states and sync¶
A Case Table is not published instantly: publishing creates a plan that a backend service executes in the background. While that happens the table has a state, and some actions are blocked.
States¶
| State | Meaning |
|---|---|
| Draft | Designed but never published, or edited after publication |
| Pending | Waiting for its plan to start |
| Active pending | Published and waiting for its plan to be added to an execution plan |
| In plan | Part of a plan that is being prepared |
| Syncing | Being applied to the database |
| Active | Published and usable |
| Error | The last plan failed |
| Deleted | Removed |
The list shows the state for each table and refreshes on its own while a plan runs.
Actions blocked while syncing¶
While a table is in Syncing, Pending, or In plan:
- View data is disabled with a message saying the data is not available in that state.
- Edit schema is disabled for the same reason.
- Opening Edit table structure from View data reports that editing is not allowed in that state.
Both actions are enabled again when the table returns to Active.
Recovering from an error¶
- Open Case Tables → Tables and find the table in Error.
- Open View data. It says Sync error. Edit to fix it, or retry.
- Choose Edit to correct the schema, or Retry.
- Retrying queues the table again: the panel reports that the table is queued and the state changes to Syncing.
No data is displayed while the table is in Error.
Follow the plan¶
Every publish, retry, import, or bulk operation creates a plan in Jobs, where you can read its timeline, approve it when it needs approval, or cancel it.
Related¶
- Jobs — plans, approvals, and retries.
- Table schema — the edits that create plans.
- Import and export — imports also run as plans.