Agentic workflows triggered on record create no longer receive the triggering record as context — executions run Interactive instead of Non-Interactive (regression since 09/09/2026, all instances)Issue SummaryAgentic workflows configured with a record-based trigger on Incident insert no longer receive the triggering record as execution context. The Orchestrator falls back to the Communicator agent and requests the record from the user, so executions run interactively and stall instead of completing autonomously.- Incident Similarity Detection- Duplicate Incident Detection Facts The workflow's trigger objective is the prompt used to invoke its agents. Updating this objective to explicitly reference the created incident record number ensures that the downstream agent receives the necessary data to execute properly. Release N/A Resolution When triggering the Incident Similarity Detection or Duplicate Incident Detection workflow, neither utterances have context of the incident number due to a missing reference in the trigger's objective.This can be fixed by adding ${number} to both trigger objectives. For exampleFor the Duplicate Incident Detection workflow"Use this newly created incident, help me find duplicate incidents by same caller, add a worknote and help create parent child relationships"to"Use this newly created incident, ${number}, help me find duplicate incidents by same caller, add a worknote and help create parent child relationships"For the Incident Similarity Detection workflow"Use this newly created incident and check for similar incidents created within the hour that are still open, add a worknotes listing them. If the channel is Automation then create parent child relationship."to"Use this newly created incident, ${number}, and check for similar incidents created within the hour that are still open, add a worknotes listing them. If the channel is Automation then create parent child relationship."