Skip to main content
September 22, 2026 Turning on self-healing for a Bolt schedule used to require connecting Slack or Microsoft Teams and picking a channel, because the healing session was triggered from inside the Slack alert thread and that thread was the only place to read it. Agent Studio now renders Bolt sessions in full, so the channel is a notification preference rather than the delivery mechanism.
  • An agent is the only requirement. On a workspace with no messaging integration the agent picker still renders, and the channel field is badged Optional with an inline hint instead of a gate that hid the picker entirely.
  • In YAML, a self_healing block with enabled: true needs agent_name only. slack_channel is omitted rather than written empty when you clear it, and the Code IDE stops underlining a file that no longer needs it.
  • Healing fires on the failure, not on the alert. The trigger moved out of the Slack alert hook, so a schedule with self-healing enabled and no Slack notifications now heals. It also heals when Slack is connected but unreachable, which used to skip silently.
  • Teams workspaces are no longer configured-but-inert. A Teams destination posts a “self-healing started” card, and a Teams webhook satisfies the Agent product’s messaging step on the setup checklist.
  • One session per failed run. Two alerts in the same channel previously produced two healing sessions for one failure.
Sessions started this way show up in Agent Studio tagged with the Bolt source, with the full transcript, status and title. Schedules that already name a Slack channel are untouched: the agent still threads into the failure notification exactly as before. See Self-healing settings and Set up self-healing. Shipped in Paradime v6.13.0.