Range Iterator Workflow Stops Midway Despite Safe Test — Fresh Task History for Investigation

Hello Pabbly Support Team,

We are following up on an existing issue related to processing more than 500 records using the Chunking / Range Iterator Architecture.

Previous forum thread:
https://forum.pabbly.com/threads/how-can-we-process-more-than-500-records-in-a-single-pabbly-connect-workflow.215189#reply-1

In the previous thread, your support team recommended disabling the final WhatsApp API and Gmail actions and running a fresh test so that the execution logs could be inspected safely.

We followed this recommendation.

What we tested

We disabled the customer-facing messaging actions (WhatsApp API and Gmail) and triggered the workflow without sending any actual customer messages.

The expected batch sequence is:

• Batch 1 → Rows 1–500

• Batch 2 → Rows 501–1000

• Batch 3 → Rows 1001–1500

• Batch 4 → Rows 1501–2000

• etc.
  
  

Each batch should execute exactly once and then move to the next batch.

What happened

The workflow still stopped midway during execution and did not complete the remaining batch intervals.

Since WhatsApp and Gmail were disabled during this test, no customer-facing messages were sent.

Fresh Task History

Task History ID:
IjU3NjYwNTZmMDYzNzA0MzU1MjY1NTUzNzUxMzM1MTY0NTQzNTBmMzIi_pc

Executed at:
Sep 04, 2026 13:46:36 (UTC+05:30) Asia/Kolkata

Workflow

Workflow: 

Workflow URL:
https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTY4MDYzNTA0MzI1MjY5NTUzNTUxMzYi_pc

What we need from Pabbly Support

Please inspect the above Task History and identify the exact reason why the workflow stopped midway.

In particular, please check:

1. Where exactly the execution stopped.

2. Why the Range Iterator did not continue to the remaining intervals.

3. Whether any previously completed batch was reprocessed.

4. Whether the next batch failed to trigger.

5. Whether the issue is related to the Iterator, Delay, workflow execution limits, or batch/range state management.

6. What configuration is required to ensure that each range is processed exactly once without restarting previous ranges.
   
   

This is important because the production workflow eventually needs to send WhatsApp messages and emails to customers. We therefore need to confirm that the batch architecture is reliable before enabling the messaging actions again.

Please review the fresh Task History and provide the root cause and recommended fix.

Thank you.

Regards,
Wellness Vibe

NIce

Hello,

Please note that we have checked your issue and also escalated your concern to the technical team. We will reach out to you once we receive an update in this regard.

Meanwhile, we appreciate your patience and understanding.

Hello,

Thank you for your patience while we investigated this issue.

Our technical team has identified and resolved the issue regarding the Range Iterator and Delay step index reset. The fix has now been deployed to production.

Could you please re-enable your workflow and run a test execution?

When checking the Task History, each Get Row(s) step should now process its sequential range as expected, without any skipped or duplicated ranges.

A quick note regarding Google Sheets: Google Sheets enforces a rate limit of 60 write requests per minute per user. To avoid hitting a 429 Rate Limit error during large batch operations, we recommend using Google Sheets → Add Multiple Rows instead of adding rows individually.

Please run the test and let us know if everything functions properly or if you need any further assistance!

Hi Hrishabh,

Thank you for your update and for deploying the fix to production.

We re-enabled the workflow and ran a test execution as requested. However, the issue still appears to be unresolved.

Test Result:

• Total records expected to be processed: 980

• Records processed successfully: 252

• Records remaining: 728

• Processing completion: Approximately 25.7%

Even after the fix, the workflow processed only 252 out of 980 records. This indicates that the workflow is still not processing the complete range as expected.

Could you please investigate the following points?

1. Range Iterator and Get Row(s) Index: Is the sequential range being reset or skipped after a certain number of iterations?

2. Delay Step: Is the Delay step causing the Range Iterator to stop, reset, or lose its index during large batch processing?

3. Task History: Could your technical team review the Task History for this execution and identify why processing stopped at 252 records?

4. Remaining Records: Why were the remaining 728 records not processed? Are there any errors, execution limits, or skipped ranges?

5. Large Batch Processing: Is there a recommended workflow configuration for processing all 980 records without skipping or duplicating ranges?

We can share the workflow details, execution logs, and Task History screenshots if required.

Please investigate this further, as processing all records accurately is essential for our automation.

We look forward to your technical team's response and a permanent resolution.

Thanks & Regards,
Kalpesh Attarde

Hi Kalpesh,

Thank you for providing the test details.

We have forwarded the exact range sequence and test results to our senior development team for an immediate re-review. They are looking into why the Range Iterator skipped ranges after the second iteration during your test run.

We will keep you updated as soon as we hear back from the developers with a resolution. Thank you for your patience!

Hi,

We have checked the issue, and all rows are now being processed.

The previous issue was caused by Google Sheets API rate limits (write requests per minute). To resolve this, we have added a delay module to queue the requests properly.

Could you please try running the workflow again and let us know if everything works smoothly?

Hi,

We have checked the issue, and all rows are now being processed.

The previous issue was caused by Google Sheets API rate limits (write requests per minute). To resolve this, we have added a delay module to queue the requests properly.

Could you please try running the workflow again and let us know if everything works smoothly?

Hi,

Just following up to check if everything is working fine now after the changes we made.

Could you please confirm whether the workflow is processing all rows successfully?

Hi,

Just following up to check if everything is working fine now after the changes we made.

Could you please confirm whether the workflow is processing all rows successfully?