Struct FlowContext 

pub struct FlowContext<'a> {

    pub tenant: &'a str,
    pub pack_id: &'a str,
    pub flow_id: &'a str,
    pub node_id: Option<&'a str>,
    pub tool: Option<&'a str>,
    pub action: Option<&'a str>,
    pub session_id: Option<&'a str>,
    pub provider_id: Option<&'a str>,
    pub reply_scope: Option<&'a ReplyScope>,
    pub retry_config: RetryConfig,
    pub attempt: u32,
    pub observer: Option<&'a dyn ExecutionObserver>,
    pub mocks: Option<&'a MockLayer>,
}

Fields

tenant: &'a str

pack_id: &'a str

flow_id: &'a str

node_id: Option<&'a str>

tool: Option<&'a str>

action: Option<&'a str>

session_id: Option<&'a str>

provider_id: Option<&'a str>

reply_scope: Option<&'a ReplyScope>

Reply scope of the originating inbound activity, when known.

Carried so async-dispatch nodes (sorla.call await) can encode the inbound thread/reply_to into the published correlation id. Without it, a wait saved against a threaded scope cannot be re-keyed on resume (the resumer would synthesize an empty thread/reply_to and miss the saved wait). See execute_sorla_call and RuntimeSessionResumer.

retry_config: RetryConfig

attempt: u32

observer: Option<&'a dyn ExecutionObserver>

mocks: Option<&'a MockLayer>