Aisensy send template task did execute wrongly, even when parameter is perfectly assigned

[iiiEM]

Your Workflow URL

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

Your Task History ID

IjU3NjUwNTY0MDYzMzA0MzY1MjZjNTUzMTUxMzc1MTYxNTQzNzBmMzIi_pc

Consent to Access & Modify

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

Hi team, I am in a big trouble,

please check the sub router of my workflow: Reminders & Engagements Till 1 Day to go reminder (Evening 8 PM) - > 5 Days to go reminder (Morning 7 AM)
here, about 100 leads did not receive the reminder, This is my first project for this client and I might lose this project if any glitch happens again.

I have assigned the parameteres perfectly, 500 leads out of 600 got the same reminder, same workflow, no changes made.

but many Aisensy tasks triggered without parameter, I am wondering if the parameter was not assigned properly, rest 500 also should not get the reminder but they got,

and if the parameter was not there, pabbly simply should have marked that tasks as RED/not executed, however due to some technical glitch of pabbly the tasks was executed successfully:
1. Pleaese help me fix this issue
2. is there anything I should do to prevent it happening again?
3. do we need to change anything in my workflow?

Team this is the first project from this client and I am so much worried about it, please guide me on this, Thank you.

 

[Preeti Paryani]

Hi @iiiEM,

We checked the workflow. This is not a Pabbly issue — it’s due to how the AiSensy API handles parameters.

Because a comma was manually added in the template parameters, when one value was missing (due to a rate limit in the previous step), the API treated it as an empty string and still accepted the request. That’s why the task showed successful instead of failed.

To fully prevent this, you would need to connect with the AiSensy team and check if they can enforce strict validation (so empty parameters throw an error instead of being accepted).

From our side, the request is being sent correctly as per the API structure.

 

[iiiEM]

I am asking a simple question, the the parameters were there from the get row task of the google sheet,
why parameters were not assigned to aisensy?

what do you mean by it?: when one value was missing (due to a rate limit in the previous step)How do I prevent this from happening team, because many leads did not receive the reminder because of this....I need your help with the solution...

please understand and help me resolve, so the purpose of using pabbly gets served...

 

[ArshilAhmad]

You are encountering a rate limit exceeded error in the Google Sheets action step. The error is from Google's end. This happens when the Google Sheets API is called multiple times within a very short period. Based on your task history, your workflow was executed multiple times in quick succession (nature of your use case), which caused this issue.

To prevent this issue, you can add a Delay After Queue step before the Google Sheets: Get Rows action step in your workflow. This will ensure there is at least a 1-minute delay between two task executions and should help prevent the error in the Google Sheets spreadsheet.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support

 

[iiiEM]

You mentioned: To prevent this issue, you can add a Delay After Queue step before the Google Sheets

honestly I did not understand how it will work, can you please do two things team?

1 do this update in my automation workflow where it is needed

2 explain me how it works
Appreciate Your help!

 

[ArshilAhmad]

1. We have added a Delay After Queue action step before the 'Get Row(s)' action step in one of the routes of your workflow on your behalf. You can similarly add a Delay After Queue step before every 'Get Row(s)' action step in your workflow.

1. Google has a rate limit that determines how many times you can execute an API endpoint within a short span of time; this is known as a rate limit.

In your workflow setup, many tasks execute at approximately the same time (because of the Delay Until step), as shown in the screenshot shared in my previous message. Because of this, the 'Get Row(s)' action step executes multiple times in a very short span of time, which causes the rate limit to be exceeded.


Adding a Delay After Queue action step will introduce a delay of 1 minute between each task execution, which should prevent the rate limit from being exceeded.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support

 

[iiiEM]

Thank you Arshil Ahmad bhai,

I don't know if you are comfortable with hindi or not, however I want to understand one thing, you mentioned "Adding a Delay After Queue action step will introduce a delay of 1 minute between each task execution, which should prevent the rate limit from being exceeded."

so if I have 1000 leads, the first lead's task will be executed and 9 AM for example, then 30th lead's task will be executed after 30 minutes as we have 1 minute of delay after each task execution and the Number 100 lead will be executed after 100 minutes of 9 AM?
-- we cant keep this logic as I will have to send 3 hours to go reminder at 9 AM only at once at the same time to all 1000 leads...

I am sorry for this confusion bhai however could you please explain or suggest me better structure for this workflow?
-- I have added this GetRow at every router because client has to update details often in the whatsapp reminders so I wanted it to be dynamic value.

Please advice karna bhai as I know that you know better and are an Expert, AssalamuAlaykum.

 

[ArshilAhmad]

Thank you Arshil Ahmad bhai,

I don't know if you are comfortable with hindi or not, however I want to understand one thing, you mentioned "Adding a Delay After Queue action step will introduce a delay of 1 minute between each task execution, which should prevent the rate limit from being exceeded."

so if I have 1000 leads, the first lead's task will be executed and 9 AM for example, then 30th lead's task will be executed after 30 minutes as we have 1 minute of delay after each task execution and the Number 100 lead will be executed after 100 minutes of 9 AM?
-- we cant keep this logic as I will have to send 3 hours to go reminder at 9 AM only at once at the same time to all 1000 leads...

You have understood that correctly. That is exactly what would happen, but currently this is the only workaround we have for the Google Sheets rate limit issue.

Currently, the minimum delay time is 1 minute. Our team is working on reducing it so you will be able to apply the delay in seconds, but that will take some time.

In the meantime, you can request Google to increase the rate limit for your account. This way, you won’t need the Delay After Queue step at all.

Usage limits | Google Sheets | Google for Developers

developers.google.com

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support