On Wed Nov 5th, 2025 I built several new automations for a client to execute some very simple actions.
When a ânext stepâ date field was changed, the automation adds a record to a related Tasks app.
We run flows like this all the time without issue.
Triggers to test started at 12:13PM but no items were created. I spent a long time reviewing the flow filters and troubleshooting with much frustration.
Checking the Org Automations Dashboard we saw 0 running, 1 scheduled, but none showing as throttled in the runs menu.
Even when trying to trigger the flow to run manually, nothing would happen. We wouldnât even see a âscheduledâ run in the system. It looked like Automations simply werenât running or responding at all.
We could however create, edit, and save new automations with no issue. They just wouldnât work or appear to trigger.
Suddenly at 1:38PM (over an hour later) all the tasks were suddenly created by the flow.
Now later in the day, we have other previously existing flows that the client relies on, but they are not running when expected.
All trigger/filter criteria are met. But no throttle or scheduled runs appear in the logs. After waiting over 30 minutes (3:14pm until 3:46pm) the automations finally ran.
Weâve never before seen this behavior with such a long wait time but no visible data on throttled flows.
Is anyone else seeing an issue like this?
Hereâs a short Loom Video example showing whatâs going on.
Luckily in the video the delay time was down to just a few minutesâŚbut still strange compared to past results we are used to seeing.
I did realize that we had made some calculation field table updates on an app that was cloned with >10k itemsâŚso maybe those calculations slowed things down.
But either way, we would expect to see the workflows had been triggered and were just in a scheduled or throttled stage (I thought thatâs what itâs done before)
Therefore I still think thereâs a bug or something weird happening. Weâve seen flows work normally for a bit, then slow down to ~30 min delay 4 or 5 times in the last 24 hours now
I think I had a conversation with Leo about this a while back and the calculation field updates (which i believe still trigger record update webhooks @andrew.cranston has flagged before) and the on record changed checks:
are âhiddenâ automations but count therefore they sit in your queue with no visibility potentially slowing down the âvisibleâ ones. I think (although I could be wrong) that Tape added some sort of logic that when there is a mass of the invisible automations in the queue then it pauses the hidden and allows some of the non hidden through.
Also if you still have record update triggers set to Any field you are adding to the âinvisibleâ queue on every record following a calculation field update therefore you are getting to the end of the invisible and then running some normal but adding to the invisible which on over 10k records can get in a right mess with little visible reason for the delay (can you tell iâve been there )
Leo can explain it way better than me
I am definitely not saying this is not a bug but I find a reason often helps that âOMG whats going on feelingâ
Thanks to @Jason who understood and described the issue spot on, and to @Tim who jumped right in and worked with me via DM to get this understood and resolved.
Definitely an issue that was caused by my user actions. But some âhiddenâ filtering actions of the flows and the breaking of automation rules when duplicated made it tricky to pinpoint.
I will be very careful to not clone workspaces with thousands of items, and then keep the cloned automations active when making calc field changes in the future.
Indeed, as @CarsonRedCliffLabs reported, there was an issue with the automation trigger where in some scenarios the selected field(s) to trigger on were lost when an app / workspace was duplicated, affecting the hosted duplicated workflow automations.
We have resolved that issue and the fix is live, so this should reduce the chances for that scenario to reappear in the future.
potentially slowing down the âvisibleâ ones. I think (although I could be wrong) that Tape added some sort of logic that when there is a mass of the invisible automations in the queue then it pauses the hidden and allows some of the non hidden through.
)