Solutionunvalidated
I manually ran it like you did (with the hash) — This exact same thing was happening to me. Tension: so when it got to it, crontab automatically cancelled it since it was producing an error. Outcome: I've set up a 5 minute timer to validate that the job ran successfully and it did.
a1fc2341-432c-462f-b35e-2b977581b800
I manually ran it like you did (with the hash) — This exact same thing was happening to me. Tension: so when it got to it, crontab automatically cancelled it since it was producing an error. Outcome: I've set up a 5 minute timer to validate that the job ran successfully and it did.