{"version":"2.1.213","anchor":"sdk-protocol-task-notification-subkind-scheduled-trigger","canonical_anchor":"sdk-protocol-task-notification-subkind-scheduled-trigger","heading":"SDK Protocol: task-notification subkind: \"scheduled-trigger\"","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.213\/e\/sdk-protocol-task-notification-subkind-scheduled-trigger","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.213","markdown":"### SDK Protocol: task-notification `subkind: \"scheduled-trigger\"`\n\n**What**\n\nThe `task-notification` origin kind now carries an optional `subkind` field. When `subkind` is `\"scheduled-trigger\"`, the turn is the automatic firing of a stored scheduled prompt.\n\n**Details**\n\n- Lets SDK integrations distinguish scheduled task deliveries from other background notifications\n- The harness frames scheduled triggers using a `[SCHEDULED TASK - AUTOMATED FIRING OF A CONFIGURED PROMPT]` prefix instead of the generic background-notification frame\n\n**Evidence**\n\nSchema addition (search for `\"Present when the delivery is the fired stored prompt of a scheduled task\/routine\"`, `\"[SCHEDULED TASK - AUTOMATED FIRING OF A CONFIGURED PROMPT]\"`)"}