We've noticed some anomalies with the results we're getting back from the search/JobSubmissions endpoint when providing it query params like:
Code: Select all
query=dateLastModified:[20240118041648 TO 20240118041911]&sort=dateLastModified
It's almost like for some of the JobSubmissions there's something cached or like a row's been locked while some other longer-running processing is happening when we make the first request, and then once that's done the dateLastModified gets updated on the JobSubmission and it appears in the results the next time the same request is made.
Is this a known issue? And what's the best workaround to handle this situation?
Kind regards,
Thomas