Error handling in the filter chain

If an error occurs in the E-Invoice Center filter chain, the complete filter chain fails. The filter chain rolls back the changes made and nothing is archived in the Seller’s archive.

How it works

When a signed e-invoice is returned from the TrustWeaver On Demand service, StreamServer sends the e-invoice through the archiving filter to a temporary storage (the runtime repository for the CollectorArchive Filter, or the specified output directory for the GenericArchive Filter).

•	If all filters complete their tasks without failures, the filter chain is successfully closed. The archiving filter then finalizes the archiving (marks the e-invoice as ready for archiving for the CollectorArchive Filter, or invokes the external archive command for the GenericArchive Filter).

•	If one filter fails, the complete filter chain fails and the archiving filter deletes the e-invoice from the temporary storage.

If the filter chain fails, the job fails. StreamServer tries to resend failed jobs from the input queue based on the Design Center Platform configuration (see Configuring input queue settings).

If a batch of invoices is sent through the filter chain and one invoice fails, the complete job fails. To avoid this, you can split the input batch into separate jobs. For example, by creating a nested Design Center Project with two jobs. The first job splits the batch and delivers the documents separately via an Internal output connector. The second job receives the documents, one by one, via an Internal input connector. The second job is where e-invoices are created, signed, and validated individually.

Retries by signing and validation filters

To prevent a filter chain from failing due to temporary network disturbances in the connection to the TrustWeaver On Demand service, the signing and validation filters try to resend failed requests up to 10 times.