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

[BUG] Matches api returning not found (404) for fast matches (ARAM) #1044

Open
gabrielfgularte opened this issue Feb 4, 2025 · 4 comments
Open
Assignees
Labels
on hold: escalated to team This issue has been escalated to the team that owns the service.

Comments

@gabrielfgularte
Copy link

gabrielfgularte commented Feb 4, 2025

Bug Description
The api https://americas.api.riotgames.com/lol/match/v5/matches/ is returning 404, although the id is obtainable via spectator api.

Problem Description
We notice that this is happening for fast matches, such as the ARAM game mode or 5v5 matches that last less than 10 minutes. The problem I'm facing is occurring in the BR1 region, and here are some match ids that we cannot retrieve details for:

BR1_3062712875
BR1_3062085479
BR1_3061990864
BR1_3062298251
BR1_3062205815
BR1_3062001612
BR1_3061158723

Expected Result
With a match id returned by the spectator api, we should successfully retrieve the match data via match api.

Actual Result
The matches api is returning 404 not found.

Developer Impact
Describe how this affects you as a developer. Please include the frequency and severity of the issue.

  • Frequency: Every API call for match IDs that last less than 10 minutes (e.g., ARAM).
  • Severity: When it happens, I lose match data and cannot determine if user has won or lost.
  • Cost: Cost: We're retroactively canceling matches, and this is causing our analytics and numbers to behave inconsistently.
  • Efficiency: -
  • User emails: ~30 support tickets per day about this issue.

Preconditions
What conditions must be met in order for this bug to occur?

  • Play an ARAM match that lasts a maximum of 10 minutes. Get the match id using the spectator api and try to retrieve the match details using the matches api within the match id.

Repro Steps
Step by step, what do you need to do to cause the bug? Note that GitHub will automagically number each step if you prefix the line with "1. "

  1. Start an ARAM
  2. Get the current match id from spectator api
  3. Finish match before 10min
  4. Try to retrieve the match using the match ID provided by the Spectator API
@geozukunft
Copy link

Do you have example ids?

@gabrielfgularte
Copy link
Author

gabrielfgularte commented Feb 4, 2025

@geozukunft

Do you have example ids?

Sure. Here's one to start with: BR1_3062712875. I'll gather more and update the issue description. Thanks.

@gabrielfgularte
Copy link
Author

gabrielfgularte commented Feb 5, 2025

@geozukunft

Do you have example ids?

So, I've gathered some additional match IDs:

BR1_3062085479
BR1_3061990864
BR1_3062298251
BR1_3062205815
BR1_3062001612
BR1_3061158723

@f3ar161 f3ar161 added the on hold: escalated to team This issue has been escalated to the team that owns the service. label Feb 10, 2025
@lucasMesquitaBorges lucasMesquitaBorges self-assigned this Feb 11, 2025
@lucasMesquitaBorges
Copy link

Hi! I'm ckecking this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on hold: escalated to team This issue has been escalated to the team that owns the service.
Projects
None yet
Development

No branches or pull requests

4 participants