GOV422
HTTP 422: the server understood your request, but the data was wrong.
Government data is full of errors. We document the ones we find: bad records, impossible values, silent schema changes, and the quiet ways federal data breaks downstream systems.
GOV422
Unprocessable entity
#0002
Record detail
"status": "Case Currently Open"
"filed_date": "2020-02-10"
"due_date": "2020-05-20"
"file_number": "B-418462.1"
"source": "GAO"
"filed_date": "2020-02-10"
"due_date": "2020-05-20"
"file_number": "B-418462.1"
"source": "GAO"
Goldschmitt & Associates filed a bid protest in February 2020. GAO set a due date of May 20, 2020. Six years later, the case is still listed as Currently Open on the GAO website. To be fair, a lot of things stopped getting resolved in mid-March 2020.
GOV422
Unprocessable entity
#0001
Record detail
"period_of_performance_start": "0226-10-31"
"calculated_fiscal_year": "227"
"source": "forecasts"
"calculated_fiscal_year": "227"
"source": "forecasts"
This federal forecast has a period of performance starting October 31, 0226 AD. That's not a typo; the government listed the year as 0226. Might need a DeLorean to meet that government requirement.