Hi Temporal team!
We are running some Temporal workflows in production, driven by certain user-generated events. Those workflows were not supposed to be long-running, and we expected them to have at most several hundred events in their history before they terminate.
However, by analyzing the workflows that have already closed I’ve noticed that some of the workflows (probably generated by “bot”-like users) have several thousand events in their histories. That made me worry if some of the active workflows might have tens of thousand events in their histories or even more, and if we should ASAP deploy a fix that would do ContinueAsNew after some time/incoming event count? To better understand the priority for that fix, I wonder if there’s a way to query active workflows by their history size in either events or bytes?
(Workflow and activity signals in that workflow are just ~100 bytes in size each, so I assume we still have some time left until history grows becomes a problem, but I’d like to be sure some active workflows are not significantly worse than the closed ones)