Unexpected `Interrupt` replies being persisted could indicate an issue with how interruptions are...
I have a workflow A that triggers another workflow B multiple times:
After a while, A fails because one of B runs has failed. Using
Is it normal that
I am using:
After a while, A fails because one of B runs has failed. Using
partition I would expect A to not fail. Looking at the replies table, i can see one of B runs resulted in a weird persisted Interrupt response (see error in thread). Looking at the reply for A, it has a similar Interrupt error.Is it normal that
Interrupt replies are persisted? I would expect not since interruption is occurring everytime a pod is stopped. Maybe I am missing something..I am using:
