Skip to content
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

Showing "Oops, there was a problem with the request" in the top of the dashboard after waking up computer #15287

Closed
mattab opened this issue Dec 18, 2019 · 4 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.

Comments

@mattab
Copy link
Member

mattab commented Dec 18, 2019

Reported in: https://forum.matomo.org/t/make-oops-there-was-a-problem-during-the-request-dismissible/35390 - I've also experienced this a few times.

In version 3.13.0 the error message “Oops… there was a problem during the request. …” always appears on top of the Dashboard after I woke up my laptop. I assume the reason is that the Wifi connection needs more time to reestablish.

It would be great if I could close that message, since everything (including Ajax like Visits in Real-Time) actually works without problem. Alternatively, the message could simply disappear after a few seconds.

Reproduce on all websites dashboard

Reproduce in Dashboard

I'm not actually sure how to reproduce it consistently but I often get this:

Screenshot from 2020-01-21 16-56-59

ideas

  • When the Real-time ajax requests fail, maybe we could diplay the error message after 3-4 or 5 consecutive fails, rather than immediately?
  • or hide the error notification that may have been displayed for the real-time widgets, whenever a successful real-time widget ajax request comes next
  • or maybe there's a better solution?
@mattab mattab added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Dec 18, 2019
@mattab mattab added this to the 4.2.0 milestone Jan 21, 2020
@gramakri
Copy link

I guess this is related to #15287 . Happens in Firefox but not in chrome.

@Findus23
Copy link
Member

@gramakri I think you meant #10578 (to cross-link it)

@mattab
Copy link
Member Author

mattab commented May 17, 2021

Maybe this will be fixed in Matomo 4.3.0 thanks to #10578

@mattab
Copy link
Member Author

mattab commented Jul 9, 2022

I haven't seen this issue recently so it was fixed AFAIK

@mattab mattab closed this as not planned Won't fix, can't repro, duplicate, stale Jul 9, 2022
@justinvelluppillai justinvelluppillai added the not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Development

No branches or pull requests

5 participants