Performance impact of Flow engine context that are in state "Waiting"

[Community Alums]

On our instance we have more than 800,000 flow context that are in the state "Waiting". About 85,000 of them were created this year.
Our instance is slow, and I am wondering what impact have these active flow context on the instance performance? I am assuming there is some sort of "cronjob" that is running daily to process these flows and must be consuming resources on the server.
Could someone guide me to a documentation or resource from ServiceNow on the impact of this. Or share some knowledge that you may have gained in your experience? Also, if there is an impact what is the best way to proceed? Some of the flows are waiting since 2019 and I am not even sure what the impact is going to be.

[New Developer_S]

hi @Community Alums ,
the following link might help .

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1179826

please mark my answer helpful ,if it is useful in solving your question.

[Community Alums]

Thanks. This definitely helps debug the cause of delays caused in the queue. I still want to know if there are any performance impact on the platform when there are a lot of flows that are waiting. I am asking the question to ensure if I should prioritize the cleanup and debug of the flows.

[tito joseph2]

A large number of flows in a waiting state can trigger influx of record watcher queries, potentially impacting the health of the database