Open
Conversation
* feat: add requester * feat: use builtin backoffs methods * force api to fail for testing purposes * add explicit list of exceptions * use validate_response approach * move super validate_response to after our custom logic * use retry_statuses config instead of hardcoded values * Revert "force api to fail for testing purposes" This reverts commit 42f0c99. * chore: minor cleanup * [pre-commit.ci] auto fixes * fix: pre-commit --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
This reverts commit e06ab22.
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
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.
We observed rare case instances of Klaviyo API returning events way in the future (events API).
Those events will update the state to the future as well, meaning that every future call will fail because a
greater-thanfilter in the API call isn't allowed.This PR is a suggestion that would eliminate the issue by filtering out future events.
Feel free to suggest alternative approaches.
Example of a payload queried on 2024-04-12. Note that datetime (which is the Event's stream replication key) is 2025-04-21: