Well, I actually want the jobid for multiple reasons. First of all, when there is a jobid, there is a job on the server and I can use the jobid for troubleshooting. This is especially important for our customers that can report a problem and then the jobid. Another use is customers with on-premises ArcGIS Enterprise solutions. They typically have client applications that start long-running gp services. It's a great feature to be able to re-attach a client to a running service. Finally, we also use jobids for logging. We obtain lists of jobids through the admin rest interface, then check and store job information, etc., since client apps might not do it. ArcGIS Server eventually cleans up old jobs. I think the biggest problem is that we are not sure when enough information is available to restore job connections. Its a minor thing to have to keep track of a complete json string rather than a single jobid.
... View more
