Consider how to handle notification that have been stuck in a sending state over time #323
Labels
kind/chore
Non functional, often repeating tasks.
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
Comments
acn-sbuad
added
status/draft
|
We'll need to wait to see how this would work with something other than Kafka. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Not sure this is an issue with the design that we have currently landed on, but we still have some instances in a sending state in the test environment database.
We should run a full analysis and consider if it is even possible for instances to end in a "forever" sending state and how to address this
There is a need for an escape from the retry loop.
Cron job som går gjennom pending og setter status tilbake til ny.
Additional Information
No response
Tasks
No response
Acceptance Criterias
No response
The text was updated successfully, but these errors were encountered: