Skip to content
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

Open
heyitsmebev opened this issue Jul 19, 2024 · 4 comments
Open

Jobs dataset returns false created_at timestamp #1199

heyitsmebev opened this issue Jul 19, 2024 · 4 comments
Assignees

Comments

@heyitsmebev
Copy link
Contributor

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.

Image

Image

@heyitsmebev heyitsmebev converted this from a draft issue Jul 19, 2024
@terrazoon terrazoon self-assigned this Aug 9, 2024
@terrazoon terrazoon moved this from 🌱 New to 🏗 In progress (WIP: ≤ 3 per person) in Notify.gov product board Aug 9, 2024
@terrazoon
Copy link
Contributor

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'> ......

@heyitsmebev
Copy link
Contributor Author

I'm no longer getting this error

@terrazoon terrazoon moved this from 🏗 In progress (WIP: ≤ 3 per person) to 👀 In review in Notify.gov product board Aug 9, 2024
@terrazoon terrazoon moved this from 👀 In review to ✅ Done in Notify.gov product board Aug 9, 2024
@terrazoon
Copy link
Contributor

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.

@heyitsmebev
Copy link
Contributor Author

This PR is intended to fix this problem: #1284

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants