Iterator causes Ultramsg to always send the same data which is the last record’s data

[chiajien]

Your Workflow URL

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

Your Task History ID

IjU3NjUwNTZhMDYzZTA0MzE1MjY1NTUzMDUxM2I1MTYxNTQzODBmMzci_pc

Consent to Access & Modify

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

When running the iterator, Ultramsg consistently sends the data from only the final record, regardless of how many records the iterator processes. Each iteration is expected to send its own corresponding data, but instead, Ultramsg outputs the same (last) record every time.

Expected behavior:

• UltraMsg should send the correct data for each iteration, matching the record being processed at that moment.

Actual behavior:

• UltraMsg only sends the data from the last record processed by the iterator.

This issue results in incorrect or duplicated messages and prevents proper sequential processing.

 

[ArshilAhmad]

Hi @chiajien,

Please allow us some time to look into this concern. We will get back to you with an update soon.