Workflow Step Failing Due to Missing ID Value from Previous Step

Hi Pabbly Support Team,
I’m encountering an issue in one of our workflows where a step that depends on a previous step’s response is failing.
Here’s what’s happening:

• The first step makes a call to the Clio API and completes successfully. I receive a success response along with the full payload, including the expected ID value.
• The next (next) step depends on that ID from the previous step. However, even though the first call succeeds, the ID value does not appear to be passed into the subsequent step during execution.
• As a result, the endpoint URL in the second step is improperly formatted (missing the ID), which causes that step to fail and stops the rest of the workflow.

Here is the workflow link: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzNDA0MzI1MjZkNTUzNzUxM2Ei_pc

Here are some Task History Ids that show the behavior:

• IjU3NjUwNTZhMDYzNTA0MzM1MjY0NTUzNjUxMzE1MTY3NTQzMDBmMzgi_pc
• IjU3NjUwNTZhMDYzNTA0MzM1MjY0NTUzNjUxMzE1MTY2NTQzODBmMzQi_pc
• IjU3NjUwNTZhMDYzNTA0MzM1MjY0NTUzNjUxMzE1MTY2NTQzNjBmMzUi_pc

Please let me know what additional details you need from me to help debug this issue.
Best regards,
Kenn Sok

Hello @kennethsok,

This issue has been escalated to our technical team for further review. Please allow us some time to look into the issue and as soon as we receive any updates, we will get back to you.

@Preeti Paryani - Is there any update on this yet? My boss sent an email regarding this but the reply wasn't relevant to the initial problem.

Thanks in advance.

Hello @kennethsok,

We have followed up with our team to share an update on this concern, once we receive an update, we will get back to you.

Also, could you please share the ticket ID for the email your boss has sent to us.

Hello @kennethsok,

This reported issue has been resolved. Please try re-executing the task histories and let us know how it goes.