Understanding and Recovering from Rate Limits (429 Errors)

What is a 429 Rate Limit Error?

When you see “HTTP error! status: 429” or “Rate limit (429) detected”, it means ChatGPT is temporarily limiting requests because too many were made in a short period.

This is ChatGPT’s way of protecting their servers from being overwhelmed and ensuring fair usage for all users.

Why Does This Happen?

Rate limits can be triggered by:

1. Batch exporting too many conversations - Syncing 50+ conversations rapidly
2. Multiple rapid exports - Clicking export repeatedly in quick succession
3. Concurrent operations - Running multiple sync operations simultaneously
4. Previous rate limit violations - ChatGPT may temporarily restrict your account

How the Extension Handles Rate Limits

Automatic Delay Between Requests

The extension lets you set a minimum and maximum delay between ChatGPT requests. It chooses a random delay within that range for each request, which helps spread out traffic during a bulk export.

For a recovery run after a 429 error, 2-3 seconds is a practical starting range. Larger exports will take longer, but the slower pace reduces request pressure.

Why random delay?

• Prevents synchronized bursts across multiple users
• More natural request pattern
• Spreads requests over time instead of sending them at a fixed interval
• Lets you balance export speed against the risk of another source-side limit

Immediate Stop on 429 Detection

When a 429 error is detected, the extension:

1. Stops all sync operations immediately - No further requests are made
2. Shows clear error message - Explains what happened and what to do
3. Saves sync progress - Records which conversations were successfully synced
4. Preserves your data - Already-synced conversations remain in Notion

Why no automatic retry?

• ChatGPT rate limits are long-lasting (minutes to hours)
• Automatic retry would trigger more 429 errors
• Could flag your account for abuse
• Manual retry gives you control over timing

What to Do When You Hit Rate Limit

Step 1: Wait Before Retrying

Recommended wait times:

• First occurrence: Wait 5-10 minutes
• Second occurrence: Wait 30 minutes
• Repeated occurrences: Wait 1-2 hours

Do not keep clicking “Begin Sync” while the rate limit is active. Repeated attempts can extend the interruption.

Step 2: Increase ChatGPT Request Pacing

Before the next bulk export:

1. Open the batch export settings
2. Find ChatGPT request pacing
3. Set Minimum delay to 2 seconds
4. Set Maximum delay to 3 seconds

If another 429 occurs at this range, stop testing and wait longer before trying again. You can also use a slower range for the next run.

Step 3: Check Sync History

1. Open the extension options page
2. Scroll to “Sync History” section
3. Find the failed sync operation
4. Review which conversations were successfully synced

Step 4: Resume Sync

After waiting, you can safely resume:

1. Enable “Skip Synced Records” (recommended)
2. Select the same sync range as before
3. Click “Begin Sync”
4. The extension will skip already-synced conversations

Real Example: Recovering a 435-Record Bulk Export

In one bulk export, ChatGPT returned a 429 after 59 of 308 selected records had been processed. The extension stopped immediately with 31 successfully synced, 28 skipped because they were already synced, and 0 failed records.

After waiting, the request pacing was changed to a random 2-3 second delay. A follow-up bulk run then processed 435 records:

• 183 records were successfully synced
• 252 records were skipped because they were already synced
• 0 records failed
• The export reached 100%

This example shows why checkpointing and “Skip Synced Records” matter: the 429 did not erase completed work, and the slower follow-up run could continue without duplicating records. A 2-3 second delay is not a guarantee for every account or export, so increase the delay or reduce the batch size if the limit returns.

Best Practices to Avoid Rate Limits

1. Use Smaller Batches

Instead of syncing all conversations at once:

• First sync: Latest 28 conversations
• Wait 10 minutes
• Second sync: Next batch with “Skip Synced Records” enabled

2. Enable Skip Synced Records

This prevents re-syncing conversations you’ve already saved:

1. Open extension options
2. Find “Skip Synced Records” toggle
3. Enable it (should be ON by default)

The recovery screenshot above shows the completed-record setting together with the slower request pacing used for the retry.

3. Avoid Concurrent Operations

Don’t run multiple sync operations at the same time:

• ❌ Don’t open multiple browser tabs running sync
• ❌ Don’t click “Begin Sync” multiple times
• ✅ Wait for current sync to complete before starting another

Understanding the Error Message

When you see a 429 error, the extension shows:

Rate limit (429) detected. Sync stopped. Please wait a few minutes before trying again.
If this happens multiple times, wait 1-2 hours before testing bulk export again.

What this means:

• ✅ Your already-synced conversations are safe in Notion
• ✅ The extension stopped to protect your account
• ⏳ You need to wait before retrying
• 🔄 You can resume where you left off

Technical Details

Request Rate

The extension uses these safeguards:

• Delay per ChatGPT request: Randomized between the minimum and maximum values you configure
• Recovery starting point: 2-3 seconds after waiting for a 429 limit to clear
• Notion requests: Use a separate automatic limiter and retry policy
• 429 detection: Immediate stop on first occurrence

Sync Progress Tracking

When sync is interrupted by rate limit:

1. Success records are saved to local storage
2. Failed items are logged with error details
3. Sync history records the interruption
4. Next sync can skip successful items

FAQ

Q: How long do I need to wait after a 429 error? A: Start with 5-10 minutes. If it happens again, wait 30 minutes to 1 hour.

Q: Will I lose my synced conversations? A: No. Already-synced conversations remain in Notion. Only the remaining items need to be retried.

Q: Can I sync faster if I’m a paid subscriber? A: No. Rate limits are enforced by ChatGPT’s API, not by the extension. All users face the same limits.

Q: Why doesn’t the extension automatically retry? A: Automatic retry would trigger more 429 errors and could flag your account for abuse. Manual retry gives you control.

Q: How do I know which conversations were synced? A: Check the “Sync History” section in the extension options. It shows detailed results for each sync operation.

Q: Can I increase the delay between requests? A: Yes. Set the minimum and maximum values under “ChatGPT request pacing.” After a 429 error, wait for the limit to clear and try a 2-3 second range. Use a slower range if the problem returns.

Q: What if I keep hitting rate limits? A:

1. Wait longer between sync operations (1-2 hours)
2. Sync smaller batches (Latest 28 only)
3. Use Auto Sync instead of manual batch export
4. Contact ChatGPT support if the issue persists

Related Topics

• Batch Sync & Backup - Learn about batch export features
• Auto Sync - Set up scheduled sync
• API Errors - Troubleshoot other API-related issues

Still Having Issues?

If you continue to experience rate limit errors after following these guidelines:

1. Check if ChatGPT is experiencing service issues: status.openai.com
2. Try syncing from a different network
3. Contact us at [email protected] with:
   • Screenshot of the error message
   • Sync history details
   • Number of conversations you’re trying to sync

We’re here to help!