Matt - You may need to provide the jobKey instead of the DBKey in your last command.
Thanks Moses. I tried grabbing the jobKey after looking up the DBKey and got this result, which when fed back into the cancel function returns the same message:
blcli_execute Job getJobKey
blcli_execute Provision cancelProvisionJob DBKey:SJobKeyImpl:2362287-3 rediscover
> The provision job is not currently running
Ok. for blcli_execute Job executeAndWaitForRunID you may need to provide the JobKey as input as well.
The execute command has always worked fine, I can start the job no probs.