All right, so I’m running into an issue where my team is stacking up automation tasks and then getting confused because things are not happening in real time. I think the primary issue with this is that 90% of the time tape response within seconds. However, during times of heavy use we experience delays because that’s how things work.
We ran into something similar with podio and globiflow added the little hover tooltip letting us know if podio was broken. That helped my team understand why changes were not happening in real time (and let’s be real, I don’t think they ever happened in real time ).
While this is a little bit different of a situation, the confusion that a lack of real time changes creates is the same.
I was thinking, maybe there’s a way that we could get the [active, running, scheduled] data on the front end of the website as my team is not looking at the automations section of the interface? Maybe a toggle on the new ‘home’ page?
we actually already have an optimization of the visibility of throttling or background jobs such as imports or similar on the roadmap and can therefore understand the request very well.
However, I’m wondering why your team has noticed a certain load on the automation queue. We just rolled out a feature a few weeks ago that ensures that automations triggered by users via create or update triggers have a higher priority and skip other jobs waiting in the queue so that they are processed immediately without delay.
The behavior you describe could be an indication that this logic is not yet working perfectly.
).
