The end of a session should not break already running asynchronous processes

Current Situation

Currently some JOC Cockpit API calls start own threads for time-consuming background tasks to run without blocking the initial API call. Most API calls are asynchronous and continue to run when the client receives the response about acceptance of the call.

At the moment, some of these asynchronous background task check the session on their own, even when the original api call has already done that.

This affects, for example, API calls executed by the JS7RestClientJob JITL Job because the JITL Job automatically calls the logout endpoint when the related API call has finished and a response is received. Due to automatic logout, the background task can fail if the used session is invalidated while the background task is still processed.

Desired Behavior

Asynchronous background tasks should not validate the session again when the original api call has already done so. Instead the relevant information should be passed from the original api call to its subsequent and asynchronous background tasks.