Blueriq Session management

The External Flow Session Lifecycle is different than usual sessions, de deviation occurs in the parent child relation of session when created by a AQ_StartProject, or the AQ_Dashboard_Widgets. These services and containers start a session as a child session of the main session.

In the image above we can see the same Runtime with two applications. "Application X" uses on of the AQ_Dashboard_Widgets to start the child session "Session A-1" in the session "Session A". "Application Y" on the other hand uses the External Flow to start a new root session "Session B" from the session "Session A". This difference is crusial in how the sessions are managed.

Session cleanup

The session cleanup for Application X and Y differ from eachother as they both use different techniques to create and management sessions.

AQ_StartProject, and AQ_Dashboard_Widgets

The AQ_StartProject, and AQ_Dashboard_Widgets all create a nested session in the current session, when looking at "Application X" this noticeable as "Session A-1" is a child session of "Session A". Direct nested sessions are cleaned up when the its parent session is closed or removed. For External Flow session this is not directly the case. 

External Flow

In "Application Y" the External Flow is used to start "Session B" from "Session A", there is a reference from "Session A" to "Session B" but it is not tightly coupled as for the sessions in "Application X". The sessions in "Application Y" should be managed as seperate sessions and therefore must be disposed of individually.