Introduction: Phase 6.

(1) This option causes the Response Routes to be executed in a separate thread and the termination of the job does not wait for their execution. See also sections Thread Queues and Threads.

There are a few things to consider though. The splitting into a separate thread only makes sense if the profile itself is not already processed in its own thread (see section Phase 1 (introduction)). For profiles with Input Agent Rule or HTTP(S) (if the response of the HTTP request should be taken from the custom class) Lobster_data deactivates the checkbox because the Response Route is needed to respond to the HTTP request. For profiles with an Input Agent of type Message, the option only has an effect if the profile is called via a synchronous message. In this case, the control is returned to the calling profile before the Response Routes are executed and the caller thus has no information as to whether a Response Route was successful. If this information is not required, the Response Routes in profiles using an Input Agent of type Message should always run in a separate thread, so that the caller cannot run in timeout problems if the target systems are unreachable. Note: If the server crashes or terminates, any jobs still to be processed that have a Response Route configured as a thread will be restarted but from the beginning, i.e. from phase 1.

(2) The base file name can be referenced with placeholder <basefile> in input fields.

(3) See section Internal Number Range and Placeholder <n>.

(4) Normally a job is not necessarily considered to be erroneous if a single Response Route fails (see section Status of Response Route - Error Behaviour). But it can be enforced with this option here.

(5) Here you can specify an additional log text for the error case.