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

Error handling for HDX Exports #3124

Open
rowasc opened this Issue Jun 29, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@rowasc
Contributor

rowasc commented Jun 29, 2018

Overview

Because of the async nature of CSV exports and HDX uploads in our system, we need a way to save and retrieve the last error of an export to show it to users, and a simple way to re-start a job if it fails for external reasons

Requirements

  • Ensure that the last HDX error for an export job is saved
  • If the error returned is related to HDX unavailability(for example 503) reset the job to "pending" so that it can be rerun later (the job queue will pick it up if it's pending)
  • Add error field to the export job table to store the resulting errors that are produced in async operations
    • this field can be null or a varchar(500)
  • Ensure that errors are displayed on the export history page in the client
    • The /jobs/{id} endpoint returns a "job_error" field that can be NULL or a string. If NULL, it means there is no error. If a string, we need to display the error to the user with the notification system.
@rowasc

This comment has been minimized.

Contributor

rowasc commented Jul 10, 2018

@willdoran can you check this? Should be a 3 I think.
The client side for it is the same as always except that we also add an error field to display instead of a generic error in the client, so it's a minor client modification and a medium modification in the backend

@rowasc rowasc removed this from the Cycle 8 milestone Jul 30, 2018

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