Troubleshooting
Action Errors
DIGGER_TOKEN is not specified
- 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
Failed to unmarshal job string
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: