Safety limits & sync protection
How 2sync protects your data with automatic safety checks
2sync includes automatic safety features that pause syncs when detecting potentially harmful operations. These protections prevent accidental mass deletions and duplicate creation, giving you a chance to review before changes apply.
What triggers a safety halt?
| Trigger | What happens | Solution |
|---|---|---|
| Multiple Deletion | Sync is about to delete more than 50% of synced items | Review pending changes, enable Bypass Halt if intentional |
| Duplicates | Sync is about to create multiple duplicate entries | Check your data source, enable Bypass Halt if needed |
When a safety halt triggers, the automation pauses and displays an error badge on your dashboard. No data is modified until you review and take action.
Safety halts exist to protect your data. Only use Bypass Halt after confirming the pending changes are intentional.
How does bypass halt work?
Bypass Halt is a toggle in your automation settings that overrides the safety check for the next sync cycle only.
- Open the automation that triggered the halt
- Review the pending changes shown in the error details
- If the changes are intentional, enable Bypass Halt
- The next sync runs without safety restrictions
- Bypass Halt resets automatically after one cycle
This ensures you consciously approve each override rather than permanently disabling protection.
When do safety limits commonly trigger?
Safety halts are expected in certain situations:
Large initial syncs: When you first connect a database with existing data, the sync may flag bulk operations as potentially harmful. For example, connecting a Google Calendar with 500 events triggers a creation halt because 2sync would add all 500 items at once.
Filter changes: Updating filters can make previously synced items fall outside the new criteria, triggering deletion warnings. For example, switching your Google Calendar filter from "All calendars" to "Work only" means all personal events that were synced are now out of scope, so 2sync detects hundreds of pending deletions and halts.
Database restructuring: Renaming or reorganizing a Notion database may cause 2sync to see items as new rather than existing.
If you frequently trigger safety halts during setup, it usually means your configuration is changing rapidly. Once your automation stabilizes, halts become rare.
What are the size and rate limits?
Each plan has recommended limits to ensure reliable sync performance:
| Limit | Description |
|---|---|
| Notion database size | Recommended maximum varies by plan; larger databases sync slower |
| Google Contacts | Maximum 25,000 contacts per Google account (Google-enforced) |
| Email count | Limited per plan based on sync time window |
| Calendar events | Limited by your plan's time window setting |
When you exceed these limits, 2sync displays a specific error code. You can resolve it by reducing the sync time window, applying filters to narrow the scope, or upgrading your plan.
See Error Codes & Troubleshooting for the full list of size and rate limit errors and their solutions.
If a safety halt persists after using Bypass Halt, or you're unsure whether the pending changes are safe, see When to contact support.
Related
- Error codes for specific error messages and solutions
- Sync problems for general troubleshooting
- Rate limits and retries for API rate limit details
- Plans & pricing for plan limits and time windows
- Connection issues for authentication and connection troubleshooting