1 of 1 people found this helpful
While the jobID is probably unique, should there be any reason the job is recreated, or something happens I doubt the same discovery would have the same job. It's a reach, but there is a potential point of failure there I think.
That was the way my thinking was leaning. I realized that a JobID is not the same as a uniqueid (like the IPAddressN column in the NodeIPAddresses table).
I'll cobble together something that merges the profileid with a homegrown id for the NPM instance.
Thanks for the input.