You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case the generation of a report fails due to the error message This report failed. It may be too big to process. We will look into it but please let us know if the problem persists., then the 'Go' button remains disabled after the error message is shown. The user can make changes to the report setting (to reduce its size), but it's impossible to run the report again afterwards.
Expected Behavior
The 'Go' button should become active again after the error message was shown.
Actual Behaviour
The 'Go' button remains disabled after the error message was shown.
Steps to Reproduce
Log in as user 7990 on staging AU (happy to provide the login details).
Go to the 'All products' report.
Run the report without filling in any fields in the report filters.
You should see the error message.
The 'Go' button remains disabled.
Animated Gif/Screenshot
Workaround
Reload the page.
Severity
bug-s5: we can live with it, only a few users impacted
Your Environment
Version used:
Browser name and version:
Operating System and version (desktop or mobile):
Possible Fix
The text was updated successfully, but these errors were encountered:
Description
In case the generation of a report fails due to the error message
This report failed. It may be too big to process. We will look into it but please let us know if the problem persists.
, then the 'Go' button remains disabled after the error message is shown. The user can make changes to the report setting (to reduce its size), but it's impossible to run the report again afterwards.Expected Behavior
The 'Go' button should become active again after the error message was shown.
Actual Behaviour
The 'Go' button remains disabled after the error message was shown.
Steps to Reproduce
Animated Gif/Screenshot
Workaround
Reload the page.
Severity
bug-s5: we can live with it, only a few users impacted
Your Environment
Possible Fix
The text was updated successfully, but these errors were encountered: