When a Notion page shows a sync error or a database view fails to refresh, the root cause is often hidden inside the Activity Log. The Activity Log records every change made in a workspace, including failed sync attempts from third-party integrations, incorrect permissions, or conflicting edits. This article explains how to locate the Activity Log, interpret sync failure entries, and take corrective actions based on the log data.
Sync failures in Notion can stem from network interruptions, expired API tokens, or permission changes on shared databases. The Activity Log stores a timestamped history of these events, allowing you to pinpoint exactly when and where a failure occurred. By auditing these entries, you can resolve issues faster and prevent future sync problems.
Below you will find a step-by-step guide to accessing the Activity Log, filtering for sync failures, and using the information to fix the underlying problem. You will also learn what each log entry means and how to distinguish between a minor sync glitch and a critical integration error.
Key Takeaways: Auditing Sync Failures in Notion
- Settings & Members > Settings > Activity Log: Displays all workspace events including sync failures from integrations and permission changes.
- Filter by event type or date range: Isolates sync-related entries so you can see exactly when and why a failure occurred.
- Click on a log entry to see details: Reveals the affected page, the integration name, and the error message such as “API token expired” or “page not found.”
What the Activity Log Records and Why Sync Failures Appear
The Activity Log in Notion is a centralized audit trail that captures every action performed in a workspace. This includes page edits, member additions, permission changes, and integration events. When a third-party tool like Zapier, Slack, or Google Drive attempts to sync data to a Notion database, the Activity Log records whether that sync succeeded or failed.
Sync failures typically appear in the log as entries with a status of “failed” or “error.” The log entry will include the name of the integration, the affected page or database, and a brief error description. Common causes for sync failures include:
- Expired or revoked API tokens for the integration
- Permission changes that removed the integration’s access to a page
- Network timeouts or rate limits from the integration provider
- Conflicting edits made by two users simultaneously
By regularly reviewing the Activity Log, you can detect these failures early and take corrective action before data becomes stale. The log retains events for up to 90 days depending on your workspace plan.
Steps to Audit Sync Failures in the Activity Log
Follow these steps to locate, filter, and interpret sync failure entries in the Notion Activity Log. Perform these actions as a workspace owner or admin.
- Open the Activity Log
Go to Settings & Members in the left sidebar. Click Settings and then select Activity Log from the menu on the left. The log displays the most recent events first. - Filter by event type
Click the Event type dropdown at the top of the log. Select Integration events or Permission changes to narrow the list to sync-related entries. You can also filter by a specific integration name if you know which tool is failing. - Filter by date range
Click the Date range filter and choose a period such as the last 24 hours or the last 7 days. This helps you focus on recent failures that are likely still affecting your workflow. - Identify entries with a failed status
Scroll through the filtered list. Look for entries that display a red icon or the word Failed next to the event description. These are sync failures. - Click the entry to view details
Click on any failed entry. A side panel opens showing the affected page name, the integration name, the exact timestamp, and the error message. For example, you might see “Access denied: API token for Zapier is invalid.” - Take corrective action based on the error
If the error says “API token expired,” go to the integration’s settings page in Notion under Settings & Members > Connections. Disconnect the integration and reconnect it with a fresh token. If the error says “Page not found,” check that the integration still has access to the page. Re-share the page with the integration if needed.
If the Activity Log Does Not Show the Sync Failure
Sometimes a sync failure occurs but does not appear in the Activity Log. This can happen when the integration itself does not report the failure back to Notion. In such cases, you must check the integration’s own logs or error dashboard. For example, Zapier and Make both provide a history of task runs that show success or failure status.
The integration’s own logs show a different error
If the Activity Log shows a successful sync but your data is missing or outdated, the issue may be on the integration side. Open the integration’s history page and look for warnings or partial failures. For instance, Zapier may show that a task completed but the data was sent to the wrong Notion database. In that case, update the integration’s mapping configuration.
The Activity Log entry is too vague
Some log entries display a generic error like “Sync failed” without a detailed reason. When this happens, re-run the sync manually from the integration’s interface and watch for a more specific error message. You can also try disconnecting and reconnecting the integration in Notion under Settings & Members > Connections.
Permission changes cause silent failures
If a page’s permissions are changed to remove the integration’s access, the Activity Log will record the permission change but not necessarily mark it as a sync failure. To catch this, filter the log by Permission changes and look for events that removed access for an integration or a guest account. Restore the integration’s access by re-sharing the page.
Notion Activity Log Limits for Different Plans
| Plan | Log Retention Period | Export Option |
|---|---|---|
| Free | 30 days | No export |
| Plus | 90 days | CSV export available |
| Business | 90 days | CSV export available |
| Enterprise | Custom (up to 1 year) | CSV export and API access |
On the Free plan, you can only see the last 30 days of activity. If you need to audit older sync failures, upgrade to Plus or Business to access the full 90-day history. Enterprise customers can request longer retention periods from their account manager.
Exporting the Activity Log as a CSV file allows you to search for specific error patterns in a spreadsheet. To export, go to Settings & Members > Settings > Activity Log and click the Export button at the top right. The CSV includes columns for timestamp, event type, user, and page name.
Now you can use the Activity Log to track down sync failures, interpret the error messages, and fix the root cause. Start by checking the log daily for any failed integration events. If you find a recurring error, consider setting up a notification in Slack or email that alerts you when a new failure is recorded. For advanced auditing, combine the Activity Log export with a script that flags repeated errors from the same integration.