I'm just testing out the new 2026 refresh, as we were previously using the-actions-org/workflow-dispatch.
with the following setup
wait-for-completion: true
sync-status: true
wait-timeout-seconds: 10
I notice that, if the timeout is reached, the dispatch step will report a success (with a warning about it not completing within timeout period
Would it make more sense to have the timeout behave as an error? failing the job. maybe only if sync-status: true?
Or is there an obvious way I'm missing for me to have this step fail if the timeout is reached?
I think the current behaviour is intentional, so I'm more asking to spark up a discussion... perhaps I'm missing the point of having this timeout.
Perhaps I should be using timeout-minutes instead
I'm just testing out the new 2026 refresh, as we were previously using the-actions-org/workflow-dispatch.
with the following setup
I notice that, if the timeout is reached, the dispatch step will report a success (with a warning about it not completing within timeout period
Would it make more sense to have the timeout behave as an error? failing the job. maybe only if
sync-status: true?Or is there an obvious way I'm missing for me to have this step fail if the timeout is reached?
I think the current behaviour is intentional, so I'm more asking to spark up a discussion... perhaps I'm missing the point of having this timeout.
Perhaps I should be using
timeout-minutesinstead