A random API action event happens even when the workflow doesn't have it

[Vyasa]

Your Workflow URL

https://connect.pabbly.com/workflow/sendwebhookdata/IjU3NjcwNTZkMDYzMzA0Mzc1MjY1NTUzNDUxMzIi_pc

Your Task History ID

IjU3NjUwNTY1MDYzZjA0Mzc1MjY4NTUzYzUxM2E1MTZiNTQzNjBmMzEi_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 I have been facing an issue in which my work flow only has 9 steps, but an extra unneeded step that I did not add is happening. I have attached the images below. I would like to know why this is happening. It's spamming my clients with unwanted messages that don't even exist in any of my workflows.

this is the work flow

the extra api action after the trigger doesn't exist in the workflow so why is this happening?

The user didnt even sign up for a financial statement anaylis course.

Hoping to understand possible solutions to this.

 

[Vyasa]

This is happening in another workflow of mine, I would appreciate to fix this ASAP.

 

[Hrishabh.pabbly]

Hi @Vyasa ,

Thank you for sharing the workflow URL, Task History ID, and screenshots.

Upon reviewing the task history, we can see that an API step (Execute API Request) is being executed, even though this step is not currently present in the workflow.

To help us identify the root cause, could you please confirm:

• Whether this API step was added earlier and later deleted from the workflow?
• And kindly share the workflow URL of the other workflow where you’re observing the same behavior.

This information will help us trace why the step is still appearing in the task history and resolve the issue as quickly as possible.

Looking forward to your response.

 

[Vyasa]

Hi @Vyasa ,

Thank you for sharing the workflow URL, Task History ID, and screenshots.

Upon reviewing the task history, we can see that an API step (Execute API Request) is being executed, even though this step is not currently present in the workflow.

To help us identify the root cause, could you please confirm:

• Whether this API step was added earlier and later deleted from the workflow?
• And kindly share the workflow URL of the other workflow where you’re observing the same behavior.

This information will help us trace why the step is still appearing in the task history and resolve the issue as quickly as possible.

Looking forward to your response.

Hi, we added the router later and what i did was i cloned this from another workflow since the steps were similar but just the data was different. So you could say it was added and then deleted.

https://connect.pabbly.com/v2/app/w...KDGkKHgsPVwECcVROACxcX10nBEkIcwFIDzwAXlN7B2Y# (The other workflows link)