Skip to Content
This documentation is provided with the HEAT environment and is relevant for this HEAT instance only.
RunnersDashboard Toolssession-trigger

session-trigger

The session-trigger processing node uses a dashboard parent output (for dashboard_users) and searchCriteria to locate sessions in the same project, then calls reprocess on a configured target-node when metadata matches.

When to use it

Use for operational workflows (refresh a stale transform after dashboard publish) where re-running one node for selected sessions is intentional.

Limitations

  • Side effect: triggers reprocessing on the platform; easy to misconfigure target-node or JMESPath.
  • Requires a dashboard upstream with dashboard_users and valid project context.
  • searchCriteria must include session (name filter) and expression (JMESPath on session metadata compared to the dashboard user).
  • Not for trainee analytics or building $heat-dataservice payloads.

Configuration

PropertyRequiredDescription
target-nodeyesSession template node name to reprocess (for example csv-input)
searchCriteriayesObject with session (string) and expression (JMESPath)
session-metadata-enrichSystem Utils (platform runner)