Ignore Rules
Ignore rules allow you to exclude certain tables from data cloning. They are configured at the twin level and apply to all clones of that pair — both manual and scheduled.
Why Exclude Tables?
Some tables are not useful to clone:
- Analytics tables —
analytics_events,page_views— often very large and unnecessary for staging - Log tables —
audit_logs,error_logs— ephemeral data - Temporary tables —
tmp_*,staging_*— working data - Sensitive tables — if you do not want to copy certain data to the target
Excluding these tables reduces clone time and the amount of data transferred.
Configuring Rules
- Go to Dashboard > [your twin]
- In the Ignore Rules section, click Add Rule
- Select the table to exclude
- Save
Rule Scope
| Aspect | Behavior |
|---|---|
| Schema | The table structure is still cloned (CREATE TABLE) |
| Data | The rows of this table are NOT cloned |
| Manual clones | The rule applies |
| Scheduled clones | The rule applies |
| Other components | Not affected (functions, triggers, etc. are still cloned normally) |
Note: Ignore rules only apply to data cloning. The table structure (schema) is always cloned to maintain the integrity of relationships and dependencies.
Editing or Removing a Rule
- Go to the twin page
- Find the rule in the Ignore Rules section
- Click Remove to delete it
The removal takes effect immediately and will apply to the next clone.
Common Examples
| Excluded Table | Reason |
|---|---|
analytics_events | Millions of rows, unnecessary in staging |
audit_logs | Audit trail data, not needed |
email_queue | Risk of sending emails from staging |
sessions | Ephemeral user sessions |
cache | Temporary data that is recreated automatically |
Next Steps
- Managing Your Twins — View and manage your pairs
- Clone Options — Other customization options