Maybe I am confused...why would you ever be working directly with a job_id to call a job remotely? I would not bother with an extra function or round trip to resolve an ID. This should suffice and survive the scenario where someone drops and recreates a job:
I agree with you 100% here...and actually prefer calling it via the job name (in case the UID changes, you're still covered) however, to assist with the OP not getting it to work, I've also had similar situations where the job would not start using the job name...so thought I'd offer one alternative
I once was asked to troubleshoot a case where the job name was not working and it turned out to be a case where the DBA that created the job copied the name from a Word document and the name included an em dash (or maybe was it an en dash). The caller was supplying a hyphen (i.e. minus sign on keyboard) which is only natural. We ended up renaming the job.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato