Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider how instances that face transient errors are handled #324

Open
Tracked by #576
acn-sbuad opened this issue Dec 4, 2023 · 2 comments
Open
Tracked by #576

Consider how instances that face transient errors are handled #324

acn-sbuad opened this issue Dec 4, 2023 · 2 comments
Labels
kind/analysis status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@acn-sbuad
Copy link
Contributor

Description

Currently instances that face a transient error are set to "new" in the database to be picked up for processing.
Are we at a risk of them ending in a constant loop where we attempt to send but never succeed and it always being set back to new?

We could consider adding a counter for how many times an email has been attempted sent for instance?

In scope

No response

Out of scope

No response

Additional Information

No response

Analysis

No response

Conclusion

No response

@acn-sbuad acn-sbuad added status/draft Status: When you create an issue before you have enough info to properly describe the issue. kind/analysis labels Dec 4, 2023
@acn-sbuad
Copy link
Contributor Author

Not sure this is somehting we need to follow up on, but creating an issue as it has been removed from the initial epic

@SandGrainOne
Copy link
Member

Postmone until after an architcture rework without Kafka.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/analysis status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

2 participants