DIGGER_TOKEN not specified. You can get one ... or self-manage a backend of Digger Community Edition (change DIGGER_HOSTNAME). You can also pass 'no-backend: true' option; in this case some of the features may not be available.
starting from v0.4.14 Digger no longer requires a token (a temporary one is generated instead). Check that you are using the latest version of BOTH cli in the workflow and the orchestrator.
if you intend to use backendless mode, you need to pass no-backend: true option in the workflow
13:17:30 main.go:973: Failed unmarshall job string: invalid character 'd' looking for beginning of valueError: Process completed with exit code 4.
This may indicate mismatch of the job parameters that are being passed to the action and what the action expects.
Things to check:
that you are running latest versions of BOTH orchestrator and action
value of the job that is passed to the workflow, under the “event” key when you expand the digger run event. Check that it looks like a valid json, smth like this: