Because we have an externally facing job status update service now, it's possible for job status updates for non-existent jobs to be recorded now. This has happened in some cases where app integrators were testing new OSG apps. This normally doesn't do any harm, but it does cause the status updates to be repeatedly propagated to the apps service, causing unnecessary work.
If the job status update endpoint receives an update for a job that doesn't exist, it should mark every job status update with that job ID as propagated in order to prevent additional propagation attempts.
Because we have an externally facing job status update service now, it's possible for job status updates for non-existent jobs to be recorded now. This has happened in some cases where app integrators were testing new OSG apps. This normally doesn't do any harm, but it does cause the status updates to be repeatedly propagated to the apps service, causing unnecessary work.
If the job status update endpoint receives an update for a job that doesn't exist, it should mark every job status update with that job ID as propagated in order to prevent additional propagation attempts.