| Info |
|---|
Levels of estimated error severity. If an error is present in the context of an API (or endpoint), it applies only to that API (or endpoint). |
| This severity level implies that the process has completely shut down and no further action is possiblealways/usually works badly. | ||||||
| This is a significant flaw that causes the system to fail. However, certain parts of the system remain functional.severity level implies that the process works badly in some cases. | ||||||
| This flaw results in unfavorable behavior but the system remains functioning. | ||||||
| This type of flaw won’t cause any major breakdown in the system. |
...
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
| Expand | |||||||||||||||
| |||||||||||||||
Description According to specification “Once you receive a change notification, you respond with HTTP 200, and add the received identifiers to a queue. Later on, in the background, you will attempt to update your locally stored information on the received entities (e.g. by calling the You SHOULD NOT try to refresh your data before sending your CNR API response. Refreshing the data (e.g. calling the A number of partner send some error codes instead. Estimated severity
Examples
| Enforceabsolutecompliance with the specificationSuggested action How communicated Email correspondence with providers, testing sessions, GitHub This error was encountered in a number of mobility systems |