kennethsok
Member
- Your Workflow URL
 - https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzNDA0MzI1MjZkNTUzNzUxM2Ei_pc
 
- Your Task History ID
 - IjU3NjUwNTZhMDYzNTA0MzM1MjY0NTUzNjUxMzE1MTY3NTQzMDBmMzgi_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 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:
https://www.loom.com/share/0b8a4c1151ce4155ab0e09bee96333e6
Here is the workflow link: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzNDA0MzI1MjZkNTUzNzUxM2Ei_pc
Here are some Task History Ids that show the behavior:
Please let me know what additional details you need from me to help debug this issue.
Best regards,
Kenn Sok
			
			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.
 
https://www.loom.com/share/0b8a4c1151ce4155ab0e09bee96333e6
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
				