Closed ADPennington closed 7 months ago
try to rebuild indexes with
python manage.py search_index --rebuild
add exception handling for elastic exceptions to bulk_create_records
look at auto-refreshing indexes (possibly in the future) - https://django-elasticsearch-dsl.readthedocs.io/en/latest/settings.html#elasticsearch-dsl-auto-refresh
closing, as #2835 has merged and #2870 addresses the remaining automation tasks
Thank you for taking the time to let us know about the issue you found. The basic rule for bug reporting is that something isn't working the way one would expect it to work. Please provide us with the information requested below and we will look at it as soon as we are able.
Description
After releasing sprint 90 code to prod, and reviewing error feedback via
frontend/admin/parsers/parsererror/
, I noticed that the error messages do not include the friendly names implemented in 2599. To be sure, I also checked the frontend for the error report associated with the errors generated, and noticed that the processing status was still "pending" and no error report was available to download.Action Taken
frontend/admin/parsers/parsererror/
and peruse parsing error messagesfrontend/data-files
page > make appropriate STT and fiscal period selections > navigate to submission history tab and check the processing status.What I expected to see
What I did see
data submission
data submission history showing pending status
parsing errors without friendly names
cloud.gov logs during data submission showing uncaught exceptions
Other Helpful Information