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

Activity Log can fail to load when recent activity includes 1000+ events #88204

Closed
cuemarie opened this issue Mar 5, 2024 · 5 comments
Closed
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Activity Log [Platform] Atomic [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. [Type] Bug

Comments

@cuemarie
Copy link

cuemarie commented Mar 5, 2024

Quick summary

Occasionally, when a customer has made a huge number of edits in a very short amount of time, Activity Log fails to load, instead just displaying greyed out bars.

Steps to reproduce

Likely hard to repro – as you'd need to make 1000 changes to blog posts or something. But theoretically:

Customer in 7841368-zen has 21 pages and 20 posts published, but had just finished manually editing every single one in the last day, when this issue began.

What you expected to happen

The Activity Log to load properly, no matter how recently a lot of activity took place.

What actually happened

CleanShot 2024-03-05 at 10 29 34@2x

Impact

Some (< 50%)

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

Atomic

Logs or notes

Workaround

The workaround is to manually append the end of the URL for the Activity Log to add a filter. It's easy to do, but not at all intuitive for customers, so it generally requires contacting support and support going through a lot of troubleshooting steps before finding. Example: p1709659923343749-slack-C03TY6J1A

📜 HISTORY

Similar Issue reported but closed here: #39772

But in the comments, this specific issue was reported a few times:

Copy link

github-actions bot commented Mar 5, 2024

Support References

This comment is automatically generated. Please do not edit it.

  • 7841368-zen
  • 5294095-zen
  • 5294718-zen
  • 5298341-zen
  • 7858954-zen
  • p9F6qB-eAH-p2#comment-59076

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Mar 5, 2024
@cuemarie cuemarie added [Pri] Normal Schedule for the next available opportuinity. and removed [Pri] Low Address when resources are available. labels Mar 5, 2024
@rickmgithub rickmgithub added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Mar 7, 2024
@rickmgithub rickmgithub moved this from Needs Triage to In Triage in Automattic Prioritization: The One Board ™ Mar 7, 2024
@matticbot matticbot moved this from In Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 7, 2024
@rickmgithub
Copy link

📌 REPRODUCTION RESULTS

As it's so difficult to reproduce marking as triaged but as it's such an edge case, leaving as normal priority rather then high.

📌 ACTIONS

Triaged

@Joshgrygiel
Copy link

Seemingly another case here: 7858954-zen

@Initsogar
Copy link
Contributor

This seems related to #88749. We just deployed a fix for this and tried rendering the Activity Log for the customer in 7841368-zen, and it is loading now.

Additional context in p9F6qB-eAH-p2#comment-59076.

@Initsogar
Copy link
Contributor

This seems related to #88749. We just deployed a fix for this and tried rendering the Activity Log for the customer in 7841368-zd-a8c, and it is loading now.

Additional context in p9F6qB-eAH-p2#comment-59076.

@Joshgrygiel this also applies for 7858954-zen. Thanks for adding that ticket as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Activity Log [Platform] Atomic [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. [Type] Bug
Development

No branches or pull requests

4 participants