-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jobs dataset returns false created_at timestamp #1199
Comments
Can't reproduce locally: Today is 8/9 and I got this: [{'created_by': {'id': '7480cdcf-fa31-42b8-a4bf-2cd4d7a9b4f4', 'name': 'GSA Kehl'}, 'created_at': '2024-08-09T17:27:27+00:00', 'updated_at': '2024-08-09T17:27:27+00:00', 'processing_started': '2024-08-09T17:28:30+00:00', 'processing_finished': '2024-08-09T17:28:31+00:00', 'job_status': <JobStatus.FINISHED: 'finished'> ...... |
I'm no longer getting this error |
I talked to Bev via slack and it looks like this problem has been resolve already in the last couple weeks. Closing as non-reproducible. |
This PR is intended to fix this problem: #1284 |
I sent a job today, 7-19-24. However, when I look at the returned API response for Jobs, the created_at field shows 7-12-24. This bug is affecting all the returned items; the created_at timestamp is incorrect for each one.
Processing_finished and processing_started seem to be correct, showing 7-19-24.
This seems to be happening for both one-off jobs and batch jobs.
The text was updated successfully, but these errors were encountered: