feat: handle LinkedEvents API timeouts for popular keywords#454
Merged
Conversation
|
KULTUS-API branch is deployed to platta: https://kultus-pr454.api.dev.hel.ninja 🚀🚀🚀 |
Add graceful degradation for LinkedEvents API timeout handling in popularKultusKeywords resolver. The resolver now continues processing remaining keyword sets even if one request fails due to timeout or connection errors. Refs: PT-1990
mhieta
force-pushed
the
seer/feat/handle-keyword-api-timeouts-SWDmNi
branch
from
1476529 to
72f74df
Compare
mhieta
changed the title
|
|
KULTUS-API branch is deployed to platta: https://kultus-pr454.api.dev.hel.ninja 🚀🚀🚀 |
|
KULTUS-API branch is deployed to platta: https://kultus-pr454.api.dev.hel.ninja 🚀🚀🚀 |
voneiden
approved these changes
Jan 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes KULTUS-API-M. The issue was that: GraphQL resolver
resolve_popular_kultus_keywordslacks error handling forConnectTimeoutErrorduring sequential external API calls, causing query failure.requests.exceptions.ConnectTimeout,requests.exceptions.Timeout, andrequests.exceptions.RequestExceptionwhen fetching keyword sets from the LinkedEvents API.popularKultusKeywordsquery continues to process other keyword sets and returns partial results even if one API request fails.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 572273
Not quite right? Click here to continue debugging with Seer.