Iterator Isn't Functioning Correctly

[HelpMeLearn]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzMjA0MzI1MjZhNTUzMzUxMzAi_pc

Your Task History ID

IjU3NjUwNTY1MDYzNDA0MzQ1MjZkNTUzMDUxMzQ1MTY3NTQzMDBmMzci_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

I've made a clone from the original workflow which I've used before & worked fine.

However, in this clone - my iterator isn't going through the entry one by one after 1 minute delay in-between. Instead, it bulk send everything & the Gmail account got rate limited. It has consumed my tasks as well.

What went wrong?

I also have another workflow that faced the same issue.

URL: https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzMjA0MzI1MjZiNTUzNTUxMzIi_pc

 

[Preeti Paryani]

Hello @HelpMeLearn,

Thanks for reaching out to us. Please try replacing the Delay For with Delay after queue and let us know if it helps.

 

[HelpMeLearn]

Hello @HelpMeLearn,

Thanks for reaching out to us. Please try replacing the Delay For with Delay after queue and let us know if it helps.

View attachment 63137

Hi, Preeti.

Thank you for your reply. I'm trying out your suggestion.

I'm facing another issue. Some of my E-mails failed to send. Of 3 instances, 1 went through.

The error: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

If it was an access token issue - wouldn't all fail?

The workflow: https://connect.pabbly.com/task/his...=IjU3NjcwNTZjMDYzMjA0MzQ1MjZmNTUzNDUxMzAi_pc#

 

[Hrishabh.pabbly]

Hi @HelpMeLearn ,

Thank you for the detailed explanation and for sharing the workflow.

Since only one out of multiple Gmail steps failed, this usually points to a connection-specific or send-as configuration issue, not the workflow logic itself.

Here are the most common reasons this happens:

1. Expired or partially invalid OAuth token
   Google tokens can expire or get invalidated intermittently. Even if some steps succeed, a specific Gmail connection may still fail.
2. Multiple Gmail action steps using different connections
   If each Gmail step is using a different Gmail connection, the failed step’s connection may need reauthorization.
3. Send-As email issue
   The value mapped in sendAsEmail must be a verified Send-As address in Gmail. If it’s not verified or permission is missing, Gmail rejects the request with this error.

What we recommend:​

• Please reconnect the Gmail account used in the failed action step.
• Ensure all Gmail steps are using the same, freshly reauthorized Gmail connection.
• Verify that the Send-As email address is properly configured and enabled in Gmail settings.

After reauthorizing, please test the workflow again. If the issue persists, feel free to share which specific Gmail step fails and we’ll take a closer look.

Looking forward to your update.