I just have 3 task consuming stage, but still the workflow is considered as a 4 task-consuming stages workflow.

[Scholars of Bedford]

Your Workflow URL

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZjMDYzNDA0M2Q1MjY0NTUzNzUxMzAi_pc

Your Task History ID

IjU3NjUwNTY1MDYzZTA0Mzc1MjZiNTUzMTUxMzY1MTY1NTQzMTBmMzYi_pc

Consent to Access & Modify

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

 

[Preeti Paryani]

Hey @Scholars of Bedford,

Thanks for reaching out.

Upon checking the task history, it appears that there are four LeadConnector actions executed in your workflow:

1. Create Contact
2. Get Pipelines
3. Create or Update Opportunity
4. Create Contact (again)

Additionally, the last Create Contact step is failing with Status Code 422 (Unprocessable Entity).

To confirm and help us investigate this properly, could you please confirm if you had added the Create Contact step twice in the workflow and later deleted/modified one of them?

Once we have your confirmation, we will proceed accordingly and escalate this to our team if required.

 

[Scholars of Bedford]

Hello Preeti, As you can see from the images of the workflow shared above, there is no stage that we have created or that is connected in the workflow. Could you please look into this and help us.

Action : Do this …

Create Contact LeadConnector V2 : Create Contact​

 

[ArshilAhmad]

So, you’re saying that you didn’t add then delete the step from your workflow. It appears on its own—is that correct?

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

 

[Scholars of Bedford]

The workflow has been there like this since starting, and we can't see that node/step. We don't know how to get rid of this.

 

[Preeti Paryani]

Hey @Scholars of Bedford,

We have escalated this issue to our technical team for further review. Please allow us some time, and we will get back to you with an update as soon as we have more information.

 

[Preeti Paryani]

Hey @Scholars of Bedford,

The reported issue has been resolved by our team. In future executions, you should not see the additional step getting executed.