You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
❗ 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
The text was updated successfully, but these errors were encountered:
evandongen
changed the title
FEATURE: Handle errostores without transaction support
FEATURE: Handle error stores without transaction support
Sep 13, 2024
philipsens
changed the title
FEATURE: Handle error stores without transaction support
Handle error stores without transaction support
Oct 14, 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:
Reporter
JJansenvr
The text was updated successfully, but these errors were encountered: