I’m actually having this same issue. I’ve been putting some outputs to check what each step is returning to see if I can figure out where the problem lies.
I’ve found that the step where it calls match_title.py systematically returns the UUID of the currently open draft instead of the one matching the input to the script. Going into the directory containing the python code and calling ./runpythonscript.sh match_title.py "TEST DRAFT TITLE" gives the same result.
If I instead do python3 match_title.py "TEST DRAFT TITLE" I get an empty result (expected as there is no Draft with this title created).
If I run both commands using a title that does appear in my library:
with runpythonscript: UUID of currently open draft
with pyhon3 call directory: UUID of matching draft.
Figured it out: In the event that PYVER_DEFAULT isn’t 3, but PYVER_3 = 3, then the command issued is python3 $1 so it calls
python3 match_title.py
It’s missing the actual argument and should match the call earlier in the script structure of
python3 $1 {@:2}
Would only experience this on systems that dont have a python command but has python3 (from home-brew).