Unclear Dealy in second Workflow same App (Airtable)

[Finspro]

Dear Pabbly Team,
in Workflow https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY4MDYzNzA0Mzc1MjZmNTUzNjUxMzYi_pc
i check Airtable records.

1 Workflow (not the one mentioned above) fires action still in 10 min frame:

Here the Step one (caused by Airtable Automation), that sets the trigger condition (2:09 pm)

Then reaction of first Pabbly Connect Workflow in the given frame of 10 minutes (2:18 pm) and sets the next trigger for second workflow:

So far ok. now we have a second Workflow (i separated them in case i need to adjust data and just want to fire the second one separately).

This second Workflow (the one i mentioned above) though takes nearly 30 minutes to fire and update the data instead of 10 as it should (execution for Update 2:48 pm!):

Here are the History Details:
History ID: IjU3NjUwNTY5MDYzNDA0Mzc1MjZkNTUzNjUxMzA1MTYyNTQzNzBmMzAi_pc

Executed at

May 08, 2025 14:48:11, (UTC+02:00) Europe/Berlin​

As this takes so long, i wonder already if the execution has an error or anything, please let me

In the first step we can also see correct the LastModified Time (without UTC+2)

So the requirements are all fine.... and i also got no delay from Airtable API reported (tested also in other application).

This is important, please let me know, why and where we have this delay when using the same Application over 2 Workflows.

Thank you in advance.
BR
Christian

 

[ArshilAhmad]

Hi @Finspro,

Task History ID - IjU3NjUwNTY5MDYzNDA0Mzc1MjZkNTUzNjUxMzA1MTYyNTQzNzBmMzAi_pc
So the issue is that you updated the data in Airtable at 2025-05-08T14:18:04 Berlin Time, but the workflow triggered at 2025-05-08T14:48:07 Berlin Time, whereas it should have triggered no later than 2025-05-08T14:28:04 Berlin Time. Is that correct?

 

[Finspro]

Hi @ArshilAhmad ,
yes, as the trigger has a action time of 10 minutes max as i understand.

 

[ArshilAhmad]

Please allow us some time to look into this concern. We will get back to you with an update soon.

 

[Finspro]

Hello @ArshilAhmad

I tested today again - two sendings of leads short after another.
The first lead was inserted into Airtable, and then the first trigger again fired in the given Frame of 10 Min. The second Workflow took again way too long, round about 30 Minutes.

The second lead was also captured by first Workflow in time, but then, the second workflow did not catch the Record at all.... ignored completely and therefore failed...

This is not reliable, please we need to understand the issue behind that!

 

[ArshilAhmad]

Hello @ArshilAhmad

I tested today again - two sendings of leads short after another.
The first lead was inserted into Airtable, and then the first trigger again fired in the given Frame of 10 Min. The second Workflow took again way too long, round about 30 Minutes.

The second lead was also captured by first Workflow in time, but then, the second workflow did not catch the Record at all.... ignored completely and therefore failed...

This is not reliable, please we need to understand the issue behind that!

Please share the Task History IDs for the two leads you submitted.

 

[Finspro]

That one here is the Task ID for the fired one that was way too late.
Task History ID -

IjU3NjUwNTY5MDYzNDA0MzE1MjZkNTUzNzUxMzE1MTYxNTQzNjBmMzci_pc​

Executed at

May 09, 2025 12:35:08, (UTC+02:00) Europe/Berlin​

The initial step was done at 12:08 and the reaction of the trigger was 12:35 - 27 Minutes instead of 10 max as shown.



The next one was recognized by first workflow in correct timeframe but not even recognized by second workflow.
Task History ID -

IjU3NjUwNTY5MDYzNDA0MzE1MjZjNTUzZDUxMzE1MTYzNTQzNzBmMzYi_pc​

Executed at

May 09, 2025 12:08:54, (UTC+02:00) Europe/Berlin​

 

[ArshilAhmad]

It seems that you are using the same table from the same base in both the trigger and action steps of these workflows, which appears to be causing the issue you are encountering.

Workflow A

Pabbly

connect.pabbly.com

Workflow B

Pabbly

connect.pabbly.com

You can use the table from the action step of Workflow A in the trigger step of Workflow B, but avoid using the same table in both the trigger and action steps of the same workflow.

 

[Finspro]

Good evening @ArshilAhmad ,

What? You mean, when i have a trigger, which is based on a field in a Base in Airtable, that launches a Workflow, and later this Workflow updates the same record in the same base, this would cause the error?
You must be kidding here.

First, the first Workflow is working as expected.
Secondly, i use the same technique in Zapier and Make and sure will have correct results in those other tools.

So please, if this would be the real issue - which is really not to believe - how could you explain this technically?
What is the exact issue here technically that causes this trouble?

Airtable automation is running perfectly, even some other part of the whole process that is also dependent on the same base is working fine, it is just Pabbly Connect Workflow that is not working as expected here.

If you would at least agree that this is not understandable or anything else, but not this strange explenation.
So, either you can manage to identify the real cause here, or you can try to convince me why this should be the problem in your opinion.

I thank you in advance for your deeper insights on this.

Regards
Christian

 

[Preeti Paryani]

Hello @Finspro,

We’ve attached a detailed video explaining the issue. Please have a look, and feel free to reach out if you have any further questions.

(1) Unclear Dealy in second Workflow same App (Airtable) | Pabbly Support

www.awesomescreenshot.com

 

[Finspro]

Good morning @Preeti Paryani , @ArshilAhmad ,

thank you very much for the explenation.

I have to say though, the delay of the longer trigger time compared to the noted 10 minutes is still not working - we tested on different times again this morning. We are located in Germany if that is helpful for checking server issues.

Latest test confirmed again the delay:

Speaking of the 10 Min frame and two involved workflows, we should be at max at 08:14 - and that should be measurable and reliable.
As this is for now more a guessing if at all.... that is not very good for the business.

Here are the steps in detail:
1. Here is the Update that causes the trigger to start from Airtable (right after inserting the new record):

2. This trigger should fire the Pabbly Workflow in the next 10 minutes as mentioned, but took 14 Minutes this time:

3. Then, after being processed the next status update for second workflow should also be processed in next 10 Minutes but took 19 Minutes

Seems not to be fixed yet - please check again for the delay here.

However, coming back to your second mentioned part - using a trigger in the same workflow with an action that updates the same record and creating "a loop" as you say.

Of course i understand, that changing the record, will also fire the trigger again, but that is why i setup a filter after the trigger, making sure, not going further after this check and therefore not having a infinite loop here.

This setup with filter to block the loop is the same in both mentioned workflows:
1. Workflow: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY4MDYzNzA0Mzc1MjZlNTUzNDUxM2Ii_pc
2. Workflow: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY4MDYzNzA0Mzc1MjZmNTUzNjUxMzYi_pc
So, the reason for now behind the two separate workflows checking and working with the same Airtable Record is as follows:

After the new Record is inserted into Airtable and prepared by the internal automation, the first trigger should recognize the updated record, then check for the right filter condition and create an Mail Text over AI and update this record on another field with the final text and setting the status in next step.

With this update happening, the second Workflow should recognize that (even if the first also "sees" the update but will be stopped by the filter should not be an issue here) and start the Filtercheck on his own. Therefore also ensuring not working with unqualified records.

The Workflow then grabs all information, sends out an Email and then updates the record again with final status.

After the last update, this record will be ignored by both workflows in future executions, until the criteria are met again.

And here comes the reason why i set it up at first in two separated ones.
Lets say, i need to adjust the Mail manually and want to resend the Email (only using Workflow 2 then here) so i can trigger that separately.

It should only give more granular control here.

I can not see why the filter that prevents a record to be processed causes further loop issues here.


Also, in my honest opinion, you do the same with so many of your example workflows of recognizing a new record in a Google sheet as example, and processing it and updating same record again. I can not see the issue here, working with data for the same record a second time in the same wokflow.

Also the delay - explained again in screenshots and notes above, seems more like a internal delay from your Application side, as i can not see these issues when testing the workflows in other automation software which i planned to retire after spending a big amount of money for Pabbly Lifetime, but it seems for now i still have so much issues, that i need to use both still

When you tell me, the setup for my workflows is not recommended, then check them in detail please and send me a proposal from your side, what and how should i setup to have NO DELAY and NO SKIPPING and still Control as planned.

I have also thought about maybe combining them into one, but this would also do the same with your mentioned "Loop" as i would have to do multiple checks and updates etc. for the same record. Plus i am not sure if i can use the Routers then as needed.

I hope the additional information will help you to investigate.

Thank you for further checks and tips in advance.
Regards
Christian

 

[Preeti Paryani]

Hello @Finspro,

This issue has been escalated to our technical team for further review. Kindly allow us some time to investigate, and we will get back to you with an update as soon as we receive more information.

Thank you for your patience.

 

[Finspro]

Thank you @Preeti Paryani , appreciate your support!
Looking forward for more info.

And as additional info, just tested again Workflow in Make, works fine and no issues with trigger and updates (even multiple updates) in same record there.

Best regards
Christian

 

[Finspro]

Hello @Preeti Paryani ,
can i have any news maybe on this please?

Thank you, regards
Christian

 

[Preeti Paryani]

Hello @Finspro,

As of now, we haven’t received any updates from our team. We’ll keep you posted and get back to you as soon as we hear anything. Thanks for your patience.

 

[Finspro]

Good evening @Preeti Paryani ,

maybe any update regarding the topic?

Thank you, regards
Christian