SystemWideMutexTimeout

Only used in situations in which multiple instances of Interpret are used with either an IMAP email server or an XML invoice input source.

Section

[Settings]

Description

To avoid deadlocks, only one Interpret instance at a time should ever access the database. This is normally the case, but if the current Interpret instance crashes, for example, no other Interpret instances would be able to continue processing.

This setting makes it possible to automatically give another Interpret instance access to the database after a specified period of time (in seconds) even if a crash occurs in the current Interpret module.

For optimal performance, the setting needs to be long enough to allow an Interpret instance to handle an invoice normally so that the process is not ended prematurely without being so long that other instances of Interpret are denied access to the database for unnecessary extended periods of time.

Testing may be required to find the appropriate setting for your system.

Valid values

  • 0 (default) - when only one instance of Interpret is used.
  • 30 or more (seconds) - it is possible to specify a number lower than 30, but then there may not be enough time to ensure that Interpret can finish processing invoices before a different instance of Interpret is given access to the database.