Maintenance & Scratch
Backup snapshots, staging tables, the error log, and the test table, none of which are part of the live model.
Not every table in the database is part of the running application. This page collects the leftovers: one-off backups, an error log, and a scratch table. Treat them as not load-bearing. Nothing in the portal should depend on them.
Failed runs
A log of failed N8N workflow executions, captured for debugging. (The table name
has a double space: Failed runs.)
| Column | Type | Notes |
|---|---|---|
id | bigint | Primary key (identity). |
created_at | timestamptz | When the failure was recorded. Defaults to now(). |
node_name | text | The workflow node that failed. |
failed_json | json | The failing payload. |
is_solved | boolean | Whether the failure has been resolved. Defaults to false. |
execution_id | bigint | The N8N execution id. |
execution_url | text | Link to the execution in N8N. |
workflow_name | text | The workflow that failed. |
Related workflows
The N8N side of error handling is documented under n8n flows. See the error handler and the reattempt / redo-error-runs workflows.
Test Table
A scratch table for experiments. It has no role in the application.
| Column | Type | Notes |
|---|---|---|
id | bigint | Primary key (identity). |
created_at | timestamptz | Defaults to now(). |
name | text | Free text. |
self_reference | bigint | → references Test Table(id). A self-reference, used to test recursive relationships. |
utctime | timestamp | Timestamp without time zone. |
timezone | timestamptz | Timestamp with time zone. |
Backup snapshots
Two _backup_* tables hold point-in-time copies taken during a data cleanup on
2026-02-27. They are plain snapshots (no primary keys, no foreign keys, no
triggers) and exist only so the cleanup could be reversed if needed.
| Table | What it snapshots |
|---|---|
_backup_bad_base_skus_20260227 | Rows removed or fixed in Base SKUs during the cleanup. |
_backup_bad_inventory_20260227 | Rows removed or fixed in Inventory during the cleanup. |
Each mirrors the columns of its source table at the time of the snapshot.
Safe to ignore, safe to drop later
These snapshots and the test table are not read by the app. Leave them alone unless you are cleaning up the database, and confirm before dropping anything dated: the date is the only record of when the backup was taken.