You’re waiting 5 minutes before checking the trace right? Your automation has a 5 minute delay before it tries to call the script. It sounds like the automation simply hasn’t gotten to that step yet based on that output.
When calling a script “directly” (e.g., script.NAME) the calling script will wait for the called script to finish. If any errors occur that cause the called script to abort, the calling script will be aborted as well.
When calling a script (or multiple scripts) via the script.turn_on service the calling script does not wait. It starts the scripts, in the order listed, and continues as soon as the last script is started. Any errors that occur in the called scripts that cause them to abort will not affect the calling script.
So if you want the automation to run the script and wait for it to finish before proceeding with the steps that follow you need to call it directly (not using script.turn_on). If you just want the script to run but the automation does not wait for it then use script.turn_on.
Now that being said, you’re saying the script does not run. Have you confirmed that by looking at the traces of the script or are you only looking at the traces of the automation?
Since the automation is kicking off the script to run in parallel it makes sense that it says the script didn’t run yet. The phrasing of that message is a bit odd I’ll admit. This node was not executed and so no further trace information is available. does not really say to me “the script was kicked off to run in parallel”. But still as long as the script is actually running at some point then its working fine.