The code itself is fine. No errors related to execution show up in the logs. Just the variable not found triggered from a follow-up sub-action. It’s not a big deal that this happens. But it drives me up the wall on a regular basis.
Comments
Log in with your Bluesky account to leave a comment
My latest course of action is to remove concurrency as much as possible. So now every action with a chat-based trigger that runs this code will use the same blocking queue.
I don't think it's a race condition per se. At least not in the sense of stomping on other actions by changing state underneath them. This code is only writing a single argument to the running action itself. I feel like there's some issue preventing the code from even executing at all.
I think this because the very first line of code is to set the default value of this argument. So it's failing to even get that far. But, SB is not throwing any errors or log messages around this action/sub-action at all.
Comments