ERR_BATCH_INCOMPLETE on Zapier: Batch processing incomplete. Root cause: A batch operation was interrupted before all records were processed. This can happen when the total processing time exceeds the platform's execution timeout, when a single record in the batch causes a fatal error, or when the target API rate-limits mid-batch. Step 1: Identify which records were processed and which were skipped. Go to zapier.com/app/history and find the incomplete batch run. Click the task to expand it. Zapier shows the last record that was successfully processed before the batch stopped. Note the record ID or position number of the last successful record — you will need this to resume from the correct point without reprocessing already-completed records. If the batch was processing a spreadsheet, note the row number of the last successful row. If it was processing CRM contacts, note the contact ID. Step 2: Reduce the batch size to stay within Zapier's execution time limit. Zapier Zaps have a maximum execution time of 30 seconds per task (or up to 15 minutes for multi-step Zaps on paid plans). If your batch is processing more records than can complete within this window, it will be cut off. In the trigger step, look for a "Limit" or "Number of records" setting and reduce it. For Google Sheets triggers, set "How many rows?" to 50 or fewer. For database triggers, add a WHERE clause to limit results. Process the remaining records in the next scheduled run. Step 3: Add a "last processed" marker to enable resumable batches. To prevent reprocessing already-completed records, add a status column to your source data. In Google Sheets, add a "Processed" column. In your CRM, add a custom field called "Zapier Processed". At the end of your Zap, add an action step that marks the record as processed (e.g., update the spreadsheet row to set Processed = TRUE, or update the CRM field). In the trigger step, add a filter to only fetch records where Processed is empty or FALSE. This makes your batch idempotent — safe to re-run without duplicating work. Step 4: Use Zapier's Looping feature for large batches on Professional plan. If you are on Zapier's Professional plan or above, use the Looping by Zapier app to process large batches reliably. Add a "Create Loop From Line Items" step that takes your full list of records and creates a loop. Each iteration of the loop processes one record as a separate task, with its own 30-second execution window. This eliminates batch timeout issues entirely because no single task is responsible for processing more than one record. The loop continues until all records are processed, regardless of how many there are. Step 5: Manually reprocess the skipped records using Zapier's Replay feature. For the records that were skipped in the incomplete batch, use Zapier's task replay feature to reprocess them. Go to zapier.com/app/history → find the incomplete run → click "Replay" if available. Alternatively, if the source data is in a spreadsheet or database, temporarily filter it to show only the unprocessed records (using the "Processed" marker from step 3) and trigger a manual run. For CRM-based batches, use the CRM's bulk export to identify which records were not updated and create a filtered view for reprocessing. Step 6: Set up a monitoring alert for future incomplete batches. Go to zapier.com/app/settings/notifications and enable email notifications for Zap errors. Zapier will email you whenever a task fails, including batch interruptions. For more granular monitoring, add a final step to your Zap that sends a Slack message or email with the count of records processed in that run. If the count is lower than expected, you will know immediately that the batch was incomplete. This proactive monitoring prevents batches from silently failing for days before anyone notices.