alive ttl for email queue #208
Merged
Conversation
This file contains 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
ice-ares
reviewed
Aug 8, 2024
|
Can u change the behaviour so that if we dont set that new ttl cfg value, the logic is what we have in master atm, and if we set it to some non zero value it behaves like in this PR? Basically instead of defaulting to the email explanation time, to default it to existing logic on master |
…n time, continue sending to user if he dont have entry in ttl
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.
Option for the FE to call same endpoint to mark that user is active and still in queue, once TTL is expired (no events from FE) - no email is sent to the user.
By default TTL is email expiration time, so it process all the queue regardless on extra endpoint calls