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
{{ message }}
This repository has been archived by the owner on Sep 12, 2019. It is now read-only.
I am building an application that is going to sit right next to the bridge, and potentially share its database. I understand my receive endpoint needs to be able to handle being called multiple times even if it has already successfully processed a receive. What are the conditions for this? Some kind of database failure? In which case, is it even worth me storing operation ids in the same database, given that it would be susceptible to the same failure mode?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am building an application that is going to sit right next to the bridge, and potentially share its database. I understand my receive endpoint needs to be able to handle being called multiple times even if it has already successfully processed a receive. What are the conditions for this? Some kind of database failure? In which case, is it even worth me storing operation ids in the same database, given that it would be susceptible to the same failure mode?
The text was updated successfully, but these errors were encountered: