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
Describe the bug
When you have a wait directive, you have the ability to say "n" to a wait to completion prompt. This skips the wait directive for the current run but if you have a second wait directive which you also say "n" to, the test for the first wait directive comes back.
To Reproduce
Create a workflow with 2 wait directives and a check which will always fail. Attempt to say "n" to the "wait for completion" prompt and it will start the second wait directive. Attempt to say "n" to this one, and it will begin the first one again.
Expected behavior
After saying n to a wait directive, it should respond as if the wait directive has passed tests.
Additional context
I have not tested this with small wait times, only with 2 wait directives with these settings
-check-every 10 -at-most 120
The text was updated successfully, but these errors were encountered:
Describe the bug
When you have a wait directive, you have the ability to say "n" to a wait to completion prompt. This skips the wait directive for the current run but if you have a second wait directive which you also say "n" to, the test for the first wait directive comes back.
To Reproduce
Create a workflow with 2 wait directives and a check which will always fail. Attempt to say "n" to the "wait for completion" prompt and it will start the second wait directive. Attempt to say "n" to this one, and it will begin the first one again.
Expected behavior
After saying n to a wait directive, it should respond as if the wait directive has passed tests.
Additional context
I have not tested this with small wait times, only with 2 wait directives with these settings
-check-every 10 -at-most 120
The text was updated successfully, but these errors were encountered: