You can end up with an infinitely delayed tracked run in the following situation:
Have a task that ends up in an Undecided approval state and is thus waiting indefinitely for approval
Have a tracked run triggered by any means (manually, push policy, etc.)
The tracked run is blocked by the pending task. The tracked run sits in the Queued state until the task is manually approved or rejected.
We had a tracked run sit in queued for 4 days unintentionally because of a task that was pending approval.
While we can notify for tasks pending approval, I have a feeling that we would want tracked runs to take precedence over tasks (if this undesirable, then you could lock the stack perhaps). We could theoretically implement this ourselves using a push policy, except that in reality, task runs pending approval don’t appear in the push policy input in_progress_runs property.
Please authenticate to join the conversation.
⬆️ Gathering votes
💡 Feature Requests
9 months ago
Get notified by email when there are changes.
⬆️ Gathering votes
💡 Feature Requests
9 months ago
Get notified by email when there are changes.