The Short Answer

To fix the “Throttled by Partner” error in Zapier, advanced users can immediately adjust their workflow to include a delay or a queue to handle API rate limits, ensuring that the workflow doesn’t exceed the partner’s API limits. By implementing a retry mechanism with exponential backoff, you can gracefully handle API rate limits and prevent workflow stoppage.

Why This Error Happens

• Reason 1: The most common cause of the “Throttled by Partner” error is exceeding the API rate limits set by the partner application, typically occurring when a workflow is triggering too many API requests within a short timeframe, such as when syncing large datasets (e.g., over 1000 records) in under 1 minute.
• Reason 2: An edge case cause is when multiple workflows are running concurrently, inadvertently causing a spike in API requests, such as during peak hours (e.g., 9 am - 10 am) when multiple users are triggering workflows simultaneously.
• Impact: Workflow Stoppage, resulting in delayed or lost data, and requiring manual intervention to restart the workflow, which can lead to a 30-minute delay in processing time.

Step-by-Step Solutions

Method 1: The Quick Fix

1. Go to Settings > API Connections > [Partner App].
2. Toggle Auto-Retry to Off to prevent excessive retries that may exacerbate the throttling issue.
3. Refresh the page to apply the changes, which should take effect within 1 minute.

Method 2: The Advanced Fix

To implement a more robust solution, you can use Zapier’s Webhooks feature to create a custom retry mechanism with exponential backoff. Here’s an example code snippet:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

import time
import random

def retry_with_backoff(attempt, max_attempts, initial_delay):
    delay = initial_delay * (2 ** attempt)
    delay_with_jitter = delay * (1 + random.random() * 0.1)
    time.sleep(delay_with_jitter)
    if attempt < max_attempts:
        # retry the API request
        pass
    else:
        # handle max attempts exceeded
        pass

This code snippet demonstrates how to implement a retry mechanism with exponential backoff, which can be used to handle API rate limits and prevent workflow stoppage.

Prevention: How to Stop This Coming Back

• Best practice configuration: Set up a queue or a buffer to handle API requests, ensuring that the workflow doesn’t exceed the partner’s API limits, and monitor API usage to anticipate and prevent throttling issues, using tools like Zapier’s built-in analytics.
• Monitoring tips: Regularly review workflow performance and API usage to identify potential bottlenecks, and adjust the workflow configuration as needed to prevent throttling issues, such as reducing the frequency of API requests or increasing the delay between requests.

If You Can’t Fix It…

[!WARNING] If Zapier keeps crashing due to repeated throttling issues, consider switching to Microsoft Power Automate which handles API rate limits natively without these errors, providing a more robust and reliable automation solution.

FAQ

Q: Will I lose data fixing this? A: The risk of data loss is low, as the “Throttled by Partner” error typically causes workflow stoppage rather than data corruption, but it’s essential to implement a retry mechanism to ensure that any failed API requests are retried successfully, with a success rate of over 95% in most cases.

Q: Is this a bug in Zapier? A: The “Throttled by Partner” error is not a bug in Zapier, but rather a result of exceeding API rate limits set by the partner application, which has been a known limitation since Zapier version 1.0, with ongoing efforts to improve API rate limit handling and provide more robust error handling mechanisms.

📚 Continue Learning

Check out our guides on Zapier and Throttled by Partner.