Delivery errors

If an error occurs after a Message is formatted and delivered to the output queue (and any retries configured for the output queue are exhausted), the job fails. For example, if the delivery fails due to an email or FTP error. As a result, the corresponding document is not delivered to the customer.

Symptom

Ad Hoc Correspondence

When the end-user submits the document in Ad Hoc Correspondence, the document closes. The end-user is not informed about the failed job. The failed job must be handled through the ordinary error handling as described below.

Correspondence Reviewer

When the end-user approves the document in Correspondence Reviewer, the document is removed from the list in Corresponding Reviewer. The end-user is not informed about the failed job. The failed job must be handled through the ordinary error handling as described below.

Solution

As a system administrator, you must attend to failed jobs to ensure that the documents are properly delivered to the customers.

Monitoring jobs using Status Messenger

You can use Status Messenger to monitor job statuses. For example, if a job fails, an e-mail can be generated to inform you about the failure. You can then take the proper actions, for example using StreamStudio Reporter.

For more information, see the Status Messenger documentation.

Resending jobs using StreamStudio Reporter

You can use StreamStudio Reporter to manually resend jobs from the queues. For example, if the connection to a customer is interrupted, you can resend the failed jobs from the output queue when the connection is re-established.

In the Design Center Platform configuration for the queues, both information and job should be stored for failed jobs. This means failed jobs remain in the queues until they are successfully reprocessed.

For more information, see the Reporter documentation.