NgDP errors
If digital mail does not work due to NgDP errors, NgDP returns different error codes and messages. The error messages are written to the workflow log. See Investigate failed processes in the workflow log in the WorkZone Operations Guide.
SmartPost performs the following action depending on the type of error. The prioritized order of actions are:
- Notify
- Try next
- Retry
The dispatch failed and the workflow is ended. A notification email that informs about the failed dispatch is sent to the process owner.
SmartPost tries to send the message to the next dispatcher in the dispatch sequence.
SmartPost tries to send the message through the same dispatcher once more.
If there are several errors, the action with the highest rank precedes other actions. For example, if there are two errors, and one error results in a Try next action and the other error results in a Notify action, the Notify action will be executed.
The table below lists NgDP errors at the time of this release. For an up-to-date list of errors, please refer to the documentation from the Agency for Digitisation (Digitaliseringsstyrelsen). Note that SmartPost does not display all errors from the list, for example if SmartPost does not yet support an NgDP feature, the related error messages are not used.
Notify action
Error that results in SmartPost performing a Notify action. The process owner may be able to resolve some the errors in the Administrative Adgang portal.
| Error | Description |
|---|---|
| contact.point.id.format.not.allowed |
The contact point ID is invalid. |
| do.not.deliver.until.date.too.early |
The "Do not deliver until date " can not be in the past. |
| do.not.deliver.until.date.too.late |
The "Do not deliver until date" is too late. |
| empty.notification.not.allowed |
Empty notification is not allowed for MeMo of the type NEMSMS. |
| file.empty.not.allowed |
One or more of the attachments in the message are empty. |
| file.extension.not.allowed |
One or more invalid file extensions in one or more files is not allowed |
| file.format.not.allowed |
The file format for one or more files is not allowed. Only the following are allowed for this type of document. |
| file.name.invalid |
The file name is invalid. |
| id.type.invalid |
Invalid ID type |
| memo.file.size.too.large |
The MeMo message is too large. |
| memo.infected |
Antivirus scan has found threats. |
| memo.invalid |
Internal NgDP error |
| message.uuid.does.not.match.file.name |
The message UUID does not match the UUID in the file name. |
| message.uuid.not.unique |
The MessageUUID is invalid. MessageUUID must be a unique. |
| notification.length.over.limit |
Notification can not be longer than {0} |
| recipient.contact.point.id.required |
Contact point must contain a contact point ID. |
| recipient.contact.point.not.allowed.for.id.type |
Contact point is not allowed for the recipient with this ID type. |
| recipient.nem.sms.is.not.allowed |
The recipient of this type can not receive nem sms messages. |
| recipient.nem.sms.subscription.mobile.number.not.verified |
The recipient has not verified the mobile number. |
| recipient.nem.sms.subscription.not.found |
The recipient does not have a NEM SMS subscription. |
| recipient.type.cannot.receive.legal.notifications |
Recipient cannot receive legal notifications. |
| sender.cpr.invalid |
The format of the CPR number is incorrect. |
| sender.cvr.invalid |
The format of the CVR number is incorrect |
| sender.do.not.deliver.until.date.not.allowed |
|
| sender.legal.notification.not.allowed |
The sender is not allowed to send legal notifications. |
| sender.mandatory.message.not.allowed |
The sender is not allowed to send mandatory messages. |
| sender.not.found |
The sender does not exist. |
| sender.organisation.id.does.not.match |
The sender organization in the message does not match when the message was received. |
| sender.system.forward.not.allowed |
Sender systems may not forward messages through Digital Post. |
| sender.system.is.deactivated |
The sender system was deactivated. |
| sender.system.is.not.activated |
The sender system has not been activated yet. |
| sender.system.not.found |
The sender system which was resolved when the message was received does not exist on the organization. |
| sender.type.not.allowed |
Only authorities can send messages to recipients of this type. |
Try next
The errors of this type occur when the recipient is not able to receive Digital Post. SmartPost tries to send the message to the next dispatcher in the dispatch sequence.
| Error | Description |
|---|---|
|
recipient.cpr.invalid |
The format of the CPR number is incorrect. |
|
recipient.cvr.invalid |
The format of the CVR number is incorrect. |
|
recipient.is.closed |
The citizen cannot receive Digital Post 2. |
|
recipient.is.exempt |
The citizen is exempted from Digital Post 2. |
|
recipient.mailbox.and.default.recipient.system.not.found |
The recipient does not have a mailbox or default recipient system. |
|
recipient.mailbox.not.found |
The recipient does not have a mailbox. |
|
recipient.not.found |
The recipient does not exist. |
Retry
| Error | Description |
|---|---|
|
wz.ngdp.connect.error |
This is a WorkZone error code. The error occurs when WorkZone cannot connect to NgDP due to connectivity issues. |