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: not loading on specific dates and activities #88749

Closed
Nic-Sevic opened this issue Mar 21, 2024 · 4 comments
Closed

Activity log: not loading on specific dates and activities #88749

Nic-Sevic opened this issue Mar 21, 2024 · 4 comments
Assignees
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Activity Log [Platform] Atomic [Pri] High Address as soon as possible after BLOCKER issues [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug

Comments

@Nic-Sevic
Copy link
Contributor

Quick summary

I've seen two cases now where the activity log is refusing to load people data for specific days. It doesn't seem like the number of changes is so large and the requests are getting responses back but nothing is loading.

looks similar to #88204

p2: p9F6qB-eAH-p2

In the latest instance I see numerous recquests for this which all return 200s and data:
https://public-api.wordpress.com/wpcom/v2/sites/220727301/activity?_envelope=1&aggregate=true&after=2023-07-19%2021%3A00%3A00&before=2023-07-20%2020%3A59%3A59&group%5B%5D=user&number=1000

If anything other than People on July 19-20, 2023 is selected, things load fine
If no filter is used, it fails to load anything, presumably because the full log includes the data above

Steps to reproduce

This is not a generic bug, it seems to only be on a few sites and the prerequisite conditions are not clear

  1. Go to unfiltered activity log and see failure to load
  2. filter by date and exclude problem date (July 20, 2023) > see load
  3. Filter to July 19-20 and select everything but People > see load
  4. Filter to July 19-20 and select only People > see fail

What you expected to happen

activity log should load and truncate if there's too much data

What actually happened

fails to load
2024-03-21 at 11 19

Impact

Some (< 50%)

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

Atomic

Logs or notes

No response

@github-actions github-actions bot added [Platform] Atomic [Pri] Low Address when resources are available. labels Mar 21, 2024
@mrfoxtalbot mrfoxtalbot added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Mar 22, 2024
@matticbot matticbot moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 22, 2024
@vparkhere
Copy link

@Automattic/yamato-backup Could we get some help on this Activity Log issue please?

@jwebbdev
Copy link
Contributor

@Initsogar started looking into this and will follow-up when we get some more information.

@jwebbdev jwebbdev added [Pri] High Address as soon as possible after BLOCKER issues and removed [Pri] Low Address when resources are available. labels Mar 27, 2024
@github-actions github-actions bot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Mar 27, 2024
@Initsogar
Copy link
Contributor

Initsogar commented Mar 28, 2024

Thanks for the report. We had some issues when returning specific user role updated events, that's more likely what it was failing especially when filtering by People. The Activity Log were expecting a summary field that wasn't returned in those scenarios.

The issue is now being fixed and discussed in p9F6qB-eAH-p2#comment-59076.

Copy link

Support References

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

  • 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 28, 2024
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] High Address as soon as possible after BLOCKER issues [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug
Development

No branches or pull requests

5 participants