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
In theory, you shouldn't be able to get a query stuck in executing state, because the only ways through that code path are to success, or raising an error.
In practice you actually can, primarily in scenarios where the interpreter exits unexpectedly. Should probably add an exit handler to wrap up state machines.
The text was updated successfully, but these errors were encountered:
This would probably require registering state machines as owned by the server instance, to ensure that any cleanup doesn't screw up those started from elsewhere.
In theory, you shouldn't be able to get a query stuck in executing state, because the only ways through that code path are to success, or raising an error.
In practice you actually can, primarily in scenarios where the interpreter exits unexpectedly. Should probably add an exit handler to wrap up state machines.
The text was updated successfully, but these errors were encountered: