Range Iterator Workflow Stops Midway Despite Safe Test — Fresh Task History for Investigation
Status: Open · Asked by WellnessVibe LLP on · 0 views
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:
Where exactly the execution stopped.
Why the Range Iterator did not continue to the remaining intervals.
Whether any previously completed batch was reprocessed.
Whether the next batch failed to trigger.
Whether the issue is related to the Iterator, Delay, workflow execution limits, or batch/range state management.
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