The process debugger supports process-wide timeout steps, with and without input transitions, and with and without breakpoints. In order to be able to stop at a timeout step that has no incoming transition, you must set a breakpoint on the timeout step. There are two ways to stop at a timeout step that does have an incoming transition. One is to set a breakpoint, and the second is step through the process if there is no breakpoint.

If you set a breakpoint on the timeout step, the timeout step should become eligible for execution. You can choose to step through or run. If you choose not to execute the step when it becomes eligible, the process should complete without running the timeout path.

If you do not set a breakpoint on the timeout step, the behavior is different depending on whether there's an incoming transition.

For a timeout step with an incoming transition and no breakpoint: you can choose to run the debug session, which will allow the process to execute without intervention as in the Process Engine (when the timer expires, the process takes the timeout path immediately). You can instead choose to step through the debug session, during which the timeout step with an incoming transition will become eligible when the timer expires.

For a timeout step with no incoming transition and no breakpoint: when the timer expires, the process debugger takes the timeout path immediately, just as in the Process Engine.