Iddle apps now getting Cyclic reference and "Workflows could not run because too many events triggered at the same time"

Is anyone else seeing pages that were not an issue for years, now showing the “too many workflows” error on single-action events such as navigation and page load?

“Workflows could not run because too many events triggered at the same time“. on single action events

Update: I’m also getting A TON of the cylic reference “Tried to update an autorun while it was already updating, cyclic“ on console.

Previous closed posts about it:

I haven’t seen that issue today, yet. But it could be just your cluster that you are on. :man_shrugging:

1 Like

Thank you for chipping in, mate. Any chance that you got the “Tried to update an autorun while it was already updating, cyclic“ on your console recently?

I’m thinking that may have to do with the database update they’re pushing this Saturday but I got a dozen thousands users bugging us about these issues, its getting tough

I haven’t been getting any of those specific issues. However, I have been getting a weird issue that when I want to Deploy my app, it takes a very long time to do so. I wonder if it is related. Something about the system slowing down for some reason.

1 Like

I’m getting that too. Sometimes it stops if I check the box to also check for issues on backend, but sometimes I need to add the &issues_off=true parameter to the URL to be able to push live.

Thanks again for the attention, J805. I really appreciate the time

1 Like

Yeah, I have a feeling it’s connected. No problem. :blush:

1 Like

This is likely an expression which references itself. It is likely through some obscure chain of expressions but is flipping between states.

That would track with your earlier post here:

2 Likes

That makes sense. :backhand_index_pointing_up:

1 Like

Hi @georgecollier! How is it going? Sorry on the delay.
It kind of was indeed! Thank you for your time!

It wasn’t exactly referencing itself per se, but the datasource and the reference were within the same parent group, and I had forgotten that sometimes this creates issues.
Also, one of them was because the group which was being used as a data source, was being hidden on a conditional, and that also caused the flickering issues.

I’m not sure why specifically, but in any way, separating the data sources far apart solved all the issues. I had seen this happen before a long time ago, but it was more of simply not working, instead of flickering, and the “workflows” could not run because…”. Scared the c*** out of me because it started suddenly while we had 30k users getting ready for an event :rofl:

Yep, it was the same situation. I deleted that post once I solved it and it seems I’ve forgot about this one. But now I’m curious on how you were able to reference the deleted post o.o