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
If the appealdocument synchronizing job encounters a document which has not the type in our appealdocumenttype list, it causes an unhandled error. Fortunately the running is not broken, but it should be handled in a more elegant way.
So: instad of this:
DETAIL: Key (type_id)=(1302893) is not present in table "api_appealdocumenttype"
we should give a more silent warning and not polluting the output with 30-rows error messages.
(Only 1302892 and 1302893 was erroneous though.)
The text was updated successfully, but these errors were encountered:
Issue
If the appealdocument synchronizing job encounters a document which has not the type in our appealdocumenttype list, it causes an unhandled error. Fortunately the running is not broken, but it should be handled in a more elegant way.
So: instad of this:
DETAIL: Key (type_id)=(1302893) is not present in table "api_appealdocumenttype"
we should give a more silent warning and not polluting the output with 30-rows error messages.
(Only 1302892 and 1302893 was erroneous though.)
The text was updated successfully, but these errors were encountered: