HTTP 202 without callback: the asynchronous feedback does not arrive
Symptom
After 202 Accepted no feedback message with accepted or rejected follows.
Cause
The receiver has no callback endpoint of the sender registered, the callback fails on authentication (mTLS, API key) or the turnaround time was not agreed.
Fix
Fix the feedback endpoint, the authentication and the maximum turnaround time in the interface agreements; monitor open 202s and escalate after the agreed period.
Check your own message for this and all other errors with the free validator: schema, code lists and consistency checks in one report.Validate a message
Attribution. Source: SIVI – VB-PUO Standard. Schemas, attribute descriptions and code lists are taken unchanged from the VB-PUO Standard (owned by the Pensioenfederatie, managed by SIVI) and shown with their release and version. Explanations, examples, error descriptions and translations are by WTP Data Lab and are not part of the standard. GitHub Stichting-SIVI/VBPUOdsk · Manual · sivi.org
