I saw a similar question about this, however, that was resolved via dependency issues. And at this point, I don't seem to have that problem that I can tell ...
I have a workflow, which has run in the past, but not since updating to Sonoma.
Debug output:
[09:13:34.934] Workflow[Script Filter] Queuing argument '(null)'
[09:13:34.944] Workflow[Script Filter] Script with argv '' finished
[09:13:34.951] ERROR: Workflow[Script Filter] Code -1: Task '/Users/ashfordp/Documents/Alfred5/Alfred.alfredpreferences/workflows/user.workflow.473C055E-E863-4FBF-A054-D91C56DBD378/status.py' failed with reason 'launch path not accessible'
If it was a dependency issue, I would expect that I cannot run that status.py script from the terminal, but I can. The script env is:
#!/usr/bin/env python3
which is installed in /usr/local/bin/python3, so I am able to execute that script.
My only other guess is that when Alfred is executing the script, /usr/local/bin is not on the path maybe?? The script is in a Script Filter Input, marked as an "external script".
Any thoughts/helpful hints would be appreciated.
Paul
Alfred: 5.1.4
MacOS: 14.1.1