3 commits

Author	SHA1	Message	Date
amoussa1229	4a5f0bc6c2	Post scheduled-run reports to a Slack channel ... Scheduled runs previously had no source channel and finished silently in the dashboard. Allow an automation to post its final report to a configured Slack channel as the bot, reusing existing Slack plumbing instead of the deferred run-completion webhook. Refs: #82	2026-06-30 20:25:33 +00:00
Johannes du Plessis	c1e46b938e	feat: add Slack Block Kit reply options (#1407) ... * feat: add Slack Block Kit reply options Co-authored-by: open-swe[bot] <215916821+open-swe[bot]@users.noreply.github.com> * docs: document Slack interactivity setup Co-authored-by: open-swe[bot] <215916821+open-swe[bot]@users.noreply.github.com> --------- Co-authored-by: open-swe[bot] <215916821+open-swe[bot]@users.noreply.github.com>	2026-06-04 10:26:09 -07:00
open-swe[bot]	eb92947806	fix: propagate Slack reply errors (#1358) ... * fix: propagate Slack reply errors Co-authored-by: Johannes du Plessis <51395795+johannes117@users.noreply.github.com> * fix: classify Slack 429 as rate_limited with retry-after Slack chat.postMessage rate limiting returns HTTP 429, which raise_for_status turned into a generic http_error and told the agent to retry immediately, ignoring Slack's retry window. Special-case 429 (threading Retry-After) and normalize the ratelimited body code before the generic HTTP path so the existing rate_limited hint actually fires. --------- Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com> Co-authored-by: Johannes du Plessis <51395795+johannes117@users.noreply.github.com> Co-authored-by: Johannes du Plessis <johannes@langchain.dev>	2026-05-28 23:11:42 +00:00