Multiple Executions and Entries for no reason

[Finspro]

Dear Pabbly Team,

i have setup a quite simple workflow between Pipedrive and Airtable.
If one criteria is set (after trigger having updated account) then create a record in one table and then in another table as well.

Now i had the case where a record got executed multiple times in same second and got more than once processed in same second in pabbly leading to multiple entries in Airtable and also blocking from Airtable due to exceeding Rate Limit for API calls.

here you can see the executions, and there have been more like these.

Please have a look at this, here is the URL for the Workflow mapping.

Pabbly

connect.pabbly.com

Thank you very much in advance.

BR
Christian

 

[ArshilAhmad]

Hi @Finspro,

The issue you are describing occurs when a user clicks on 'Save & Send Test Request' multiple times, which, in turn, creates multiple webhooks in the application, causing the workflow to execute that many times.

To fix this, disable the workflow in which you are facing the issue and set up a new workflow from scratch (without cloning).

Please ensure that while setting up the 'Pipedrive: Updated Person' trigger step, you click on 'Save & Send Test Request' only once.

 

[Finspro]

Hi @ArshilAhmad ,
thank you for your message, but i have not test running yet. The workflow is active and was only triggered by the trigger application (Pipedrive) - no one pressed for test here.
I think this is another issue.

OR do i misunderstand anything here?

 

[ArshilAhmad]

You are using the 'Update Person' trigger step in your workflow. Please note that the 'Update Person' trigger step will trigger even if there is a minor change in a person's details. It is possible that some minor changes were made to the person details, resulting in the same details being recorded in your Airtable again.

We recommend using the 'New Person' trigger event instead, which will ensure that your workflow is triggered only for newly added persons to your Pipedrive account.

 

[Finspro]

Hello @ArshilAhmad ,
although i thank you for the idea, but this is absolutely NOT the right way.

I even miss a trigger that says "New or updated record" - both in one. but as we do not have them, i need to use the updated record.

Imagine, you could not use the updated record in CRM, there is always the workflow of updating existing records and give them new settings, new values, new status etc.
Depending on exactly these changes we need to do the workflows and this is what Pabbly should handle.

Instead of proposing to cut your own functionalities it would be helpful to understand why the trigger fired multiple times when there was no test execution and the record was updated only once - i checked that in the change protocol of the record in CRM.

Of course, i need to do a duplicate check for transferring the account again, this is not the point here but what is needed also, is the check for the multiple execution as this caused my API connection to airtable to be paused which can cause other additional issues with other transfers or using of other workflows.

Could you therefore please double check again for the issue?

Thank you, regards
Christian

 

[ArshilAhmad]

Could you please share two Task History IDs where your workflow was triggered with the exact same data?

 

[Finspro]

Hi @ArshilAhmad ,
sorry for this late response, i was sick and not working.
Also, happy new year

In the screenshot up in the post i showed one of the chains you can check for the sent data.
Hopefully you can find something - we would love to migrate completely from Zapier to Pabbly but yet still have some hickups with first tests.

Thank you in advance.
BR
Christian

 

[ArshilAhmad]

Hi @Finspro,

Wishing you a Happy New Year as well! We reviewed a few Task History IDs shared in the screenshot above, but they showed minor differences in the data received in the trigger step. Therefore, we need two Task History IDs triggered with the exact same data. Could you please share two such Task History IDs so our team can look into this issue?

 

[Finspro]

We had the same meanwhile for new transmissions as well, so the problem persists.
I also will try to set somehow a border with the process but this shouldnt be that way, right?

 

[ArshilAhmad]

Based on your two most recent Task History IDs, we can see that although they appear to be triggered by the same data, there are minor differences between the data received in the two executions. This behavior is expected because the workflow has an 'Updated Person' trigger step.

Task History ID - IjU3NjUwNTZmMDYzNzA0M2Q1MjZmNTUzNjUxMzE1MTYxNTQzOTBmMzEi_pc

Task History ID - IjU3NjUwNTZmMDYzNzA0M2Q1MjZmNTUzNjUxMzE1MTYxNTQzOTBmMzEi_pc

Diffchecker - Compare text online to find the difference between two text files

Diffchecker will compare text to find the difference between two text files. Just paste your files and click Find Difference!

www.diffchecker.com

I also will try to set somehow a border with the process but this shouldnt be that way, right?

We're not sure what you mean by this statement. Could you please elaborate further on what border are you referring to?

 

[Finspro]

Hi @ArshilAhmad ,
thank you so much for your information, i am honest, i have no idea why we have different sendings here, all we do is giving an update on the accounts person to be triggered to be sent from pipedrive to airtable.
I am not sure why this happens this way.

With the "border" i mean to maybe adjust my Connect Workflow a bit?
I added an update step during the workflow process that should ensure that the trigger is not fired a second time.
Can you maybe check if this is a recommended Solution or is there any other certain way as best practice?

 

[ArshilAhmad]

I am assuming you will update the complete details of a person and, finally, update the 'Current Im 0 Value' field to 'A2024' to ensure that only completely updated persons execute the steps after the filter. If so, then this is the correct approach for your use case.

Pabbly

connect.pabbly.com

 

[Finspro]

@ArshilAhmad , Yes, we have a contact, which is getting updated.
As the trigger is not able to check for just a certain field update i did the following.
If the update trigger is fired, the naxt step is to have a filter that checks for a certain field to be updated as you described.
Then a following step is to reset this to ensure the record is not considered again.

But is it possible for you to see why we had another sending if we just had on Pipedrive one single update? We did one update in Pipedrive and the trigger sent multiple records.

We saw that on multiple examples - is it possible that internal processes like writing the change log for the record (pipedrive internal process) would also be considered as an update?

I just need to understand what is going wrong here, as for another update process in Pipedrive we did not have this happening.

 

[Preeti Paryani]

Hello @Finspro,

We've noticed that even minor updates, like changes to person details or internal change logs in Pipedrive (e.g., updated email send count), are triggering the workflow. The filter check should prevent unnecessary workflow executions, but these small updates are still being processed.

 

[Finspro]

Hi @Preeti Paryani ,
thank you, so considering your feedback - how would it be possible that i can just use one certain update and nothing else (no more trigger fireing) for the workflow then correctly?

Would be the only recommended way from pabbly then to use a filter step like i did? So this way i would only stop it after it started, right?

 

[ArshilAhmad]

Hi @Preeti Paryani ,
thank you, so considering your feedback - how would it be possible that i can just use one certain update and nothing else (no more trigger fireing) for the workflow then correctly?

It's not possible to trigger the workflow for certain updates while excluding others.

Would be the only recommended way from pabbly then to use a filter step like i did? So this way i would only stop it after it started, right?

Yes, adding the Filter as you have done is the only workaround for now.

 

[Finspro]

Thank you both.
Then i will continue to work this way for now.
Will report if i have further issues later on.

BR
Christian