🔗 Source article (Salesforce): Click here
Interruption by eHealth
Pending messages in outbox are usually related to eHealth interruptions. The status of eHealth can be consulted here.
Normally UM will make 3 different sending attempts in case of an eHealth downtime. If the downtime lasted longer, these messages will go into error. To send them again you will need the following queries to be executed in the database:
Important:
stop service unified-messaging before making changes to the DB
take a backup of the DB before making changes
update dbo.message set sendStatus='SENDING_FAILED' where sendStatus='SENDING_FAILED_PERMANENTLY'
UPDATE MessageSendStatus SET numberOfSendAttempts = 0 WHERE numberOfSendAttempts > 1
In case they ended up in the error folder, the only way to reprocess them is to move them from the error folder to the original send folder. UM will then pick them up again for sending. By default, this is C:\unifiedmessaging\out.
You can also check this path via Settings < File interface < Folder to send.
Out-of-office
The recipient should always be checked if messages cannot be sent. When the out-of-office of a healthcare provider is set, messages cannot be sent. In the logs which can be found by default under C:\Programfiles\Unifiedmessaging this is shown under eHealth error code 826. More info about the eHealth error codes can be found here.
Invalid eHealth certificate
Another possibility is that the recipient does not have a valid eHealth certificate. This can be checked through HealthPages.
[ IMAGE: 149.png ]