InterruptErrors should differentiate between the prior execution that was interrupted, and the current execution that raises the rescuable exception #1382
The previous execution that was interrupted and is left in an unfinished state
The current execution which has detected that the previous execution was left unfinished, and signals to this to the application by raising an InterruptError
Currently, both records are updated with the same InterruptError which is confusing. I think there should be a different error recorded on the execution(s) that are interrupted to differentiate and explain why an interrupt results in 2 different executions (I just confused myself with this).
Currently when an execution is interrupted and then retried and handled via the InterruptErrors extension, there are 2 executions in play:
Currently, both records are updated with the same
InterruptErrorwhich is confusing. I think there should be a different error recorded on the execution(s) that are interrupted to differentiate and explain why an interrupt results in 2 different executions (I just confused myself with this).