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

When an export's status shows failed, if I refresh the page it switches to complete #3140

Open
rowasc opened this Issue Jul 6, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@rowasc
Contributor

rowasc commented Jul 6, 2018

Describe the bug
When an export's status shows failed, if I refresh the page it switches to complete

Where was the bug observed
http://csvexportsforever.v3-qa.ush.zone/

To Reproduce
Steps to reproduce the behavior:

  • Have an export job "pending" in the database
  • Refresh the client in the export history page. You should see "pending" as status
  • Setup the export job status as Failed in the database.
  • Refresh the client in the export history page. You will see "complete" or data_export.exported_to_cdn as status

Expected behavior

  • Have an export job "pending" in the database
  • Refresh the client in the export history page. You should see "pending" as status
  • Setup the export job status as Failed in the database.
  • Refresh the client in the export history page. You should see "Failed" as status.

Is there a workaround? What is it.
No

Screenshots

See screenshot below

image

  1. When an export status shows pending or failed then i refresh the page the status switches to complete.

Screenshot after export

image

Screenshot after refreshing the page

image

Desktop Hardware Details (please complete the following information):

  • OS: Windows 10
  • Browser Chrome
  • Version: 66.0.3359.139

Smartphone Hardware Details (please complete the following information):
N/A
Additional context
Add any other context about the problem here.

@rowasc

This comment has been minimized.

Contributor

rowasc commented Jul 6, 2018

@jrtricafort this looks pretty bad. :/ Eve found it while testing #3080, its not related to the fix but its obviously problematic. Can you prioritize?

@rowasc rowasc added the P2 - Normal label Sep 28, 2018

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