You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Scheduler consumes the execution queue for reporting only.
It uses it to know when a trigger should have started an execution but the execution is not already started to be able to emit a WARNING.
As consuming the execution queue is costly, we may revisit this implementation and the cost/benefit balance.
The text was updated successfully, but these errors were encountered:
Would a periodic check (e.g., every minute) for missed trigger executions be acceptable instead of continuous queue consumption? This could significantly reduce the system load while still maintaining the warning functionality.
The Scheduler consumes the execution queue for reporting only.
It uses it to know when a trigger should have started an execution but the execution is not already started to be able to emit a WARNING.
As consuming the execution queue is costly, we may revisit this implementation and the cost/benefit balance.
The text was updated successfully, but these errors were encountered: