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
I've noticed a nested flow was not executing on_success or on_done callbacks, even though it ran successfully. Actually, only the first flow would execute.
No luck. By doing so, Flow enters on an infinite loop waiting for the synchronous receive. Async works fine (no need for any change). May need a couple tweaks on the Manager or how the Driver works, but since nothing is documented it's hard to spot what without going "all in".
The text was updated successfully, but these errors were encountered:
Hit this bug again on a non-nested callback. on_success, on_done and on_fail callbacks are completely ignored on Synchronous driver (haven't tested with async but it probably would work).
I've noticed a nested flow was not executing
on_success
oron_done
callbacks, even though it ran successfully. Actually, only the first flow would execute.The
case
above led me to believe only the flow with counter 1 was being executed. Counter is not documented so I'm assuming it's a stack counter.I've tried adding a handler for
{flow, n}
, and updating the:heflow
process with{pid, n - 1}
, similar to how it's defined on__finish__
:No luck. By doing so, Flow enters on an infinite loop waiting for the synchronous
receive
. Async works fine (no need for any change). May need a couple tweaks on the Manager or how the Driver works, but since nothing is documented it's hard to spot what without going "all in".The text was updated successfully, but these errors were encountered: