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.