I worked around the problem with the console log before by adding something like a “sleep 10” command which apparently gave enough time for the log to appear in the console. Not a fix but at least it helped me figure out which command failed. I would expect something like this to happen when running commands in the background/asynchronously but not when running commands in the foreground/synchronously.