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

Failed delivery of invoice to corner 4 #3

Open
PatrickVHL opened this issue Jun 14, 2021 · 2 comments
Open

Failed delivery of invoice to corner 4 #3

PatrickVHL opened this issue Jun 14, 2021 · 2 comments

Comments

@PatrickVHL
Copy link
Contributor

PatrickVHL commented Jun 14, 2021

MLR and Invoice Response do not cover the case where communication between corner 3 and corner 4 fails (persistently). F.e. after 5 retries still no successful delivery of message.

@PatrickVHL
Copy link
Contributor Author

The discussion within the Post-Award Community (PoAC) about this topic is still open.

Part of the community believes that the Message Level Response is the best way of communicating the failure. Advantages are that the MLR is already available and could easily be extended to accommodate an error code for this type of failure. On the other hand the MLR is specifically used for failures within the domain of schematron business rule violation. MLR would lose it's specific purpose and become a more generic message.

The other part of the community believes this should not be done within a Message Level Response or an Invoice Response. The suggestion would be to use the failure to deliver an Invoice Response to C1 within a timeframe (f.e. 1 hour) to establish a failure in the communication between C3 and C4. The downside

@wimkok
Copy link
Contributor

wimkok commented May 17, 2022

The communication about not being able to deliver adocument form C3 to C4 must go to sending endpoint C1.
C2 is responsible to deliver a correct document to C3. Communication about correctness of documents is done by MLR form C3 to C2 because responsebility about correctness of document lies with C2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants