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

Handle error stores without transaction support #6428

Open
jjansenvr opened this issue Mar 12, 2024 · 0 comments
Open

Handle error stores without transaction support #6428

jjansenvr opened this issue Mar 12, 2024 · 0 comments
Milestone

Comments

@jjansenvr
Copy link
Contributor

jjansenvr commented Mar 12, 2024

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗

Describe the issue
Currently the retry from errorstore and the result (success or failure) is managed using a transaction, this means the record in the errorstore is rolled back if the error occurs

I would like to handle this differently using status field in the errostore table.
Advantages:

  • The errorstore does not need to be a transactional data source
  • Easier to store the lates error result.
  • we can add columns for last resend date and number of retries
  • we can add column with a resend history logging the user, resend date and the number of retries
  • it will be easier to create a scheduled process re-sending the messages

Reporter
JJansenvr

@nielsm5 nielsm5 added this to the 8.3 milestone Mar 18, 2024
@evandongen evandongen changed the title FEATURE: Handle errostores without transaction support FEATURE: Handle error stores without transaction support Sep 13, 2024
@philipsens philipsens changed the title FEATURE: Handle error stores without transaction support Handle error stores without transaction support Oct 14, 2024
@nielsm5 nielsm5 modified the milestones: 9.0, 9.1 Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants