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
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:
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. "
Start an ARAM
Get the current match id from spectator api
Finish match before 10min
Try to retrieve the match using the match ID provided by the Spectator API
The text was updated successfully, but these errors were encountered:
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.
Preconditions
What conditions must be met in order for this bug to occur?
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. "
The text was updated successfully, but these errors were encountered: