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.