← Back to home

Changelog

What changed in Asyncbot, newest first.

2.6.3 - 2026-09-02

  • Adding time off that overlaps time off you already have merges the two into one range. Consecutive ranges and ranges with a gap stay separate. It used to add a duplicate row every time.

2.6.2 - 2026-09-02

  • Reinstalling inside the 14-day grace now gets a DM too. It says welcome back, names the rotations that came back, and lists the channels to invite the bot into again. A first install still gets the first-install welcome.

2.6.1 - 2026-09-02

  • After Add to Slack, the site shows your workspace name in the top-right badge. It used to show the raw team id.

2.6.0 - 2026-09-02

  • Asyncbot stopped saying “on duty” and “on-call”. A rotation now just says who’s on: “Ana is on release”, “You’re off triage”, “Nobody is on it yet”. The list marker is (on). Nothing about how rotations work changed, only what the bot calls things.
  • The reason: the old wording made this sound like a pager for incident teams. It was never only that. A rotation is whatever your team takes turns on: triage, releases, support, reviews, the thing nobody wants to own twice in a row.
  • The Slack app description says that now too: “I track your team’s rotations so everyone knows who’s responsible—no meetings needed.”
  • The daily post header is “Today” instead of “On duty today”.
  • If connecting Slack fails, you land back on the pricing page instead of the homepage, so you can start again from the plan you picked.
  • Signing in and installing now fail differently. A failed sign-in tells you the sign-in failed, instead of the generic error it used to show.
  • A rotation now needs a channel. Create and Edit both ask for one, so a rotation always has somewhere to post.
  • Editing members counts the workspace as the edit leaves it, so removing people from a rotation on the Free plan no longer trips the member limit.
  • Asyncbot asks Slack for fewer permissions. It no longer requests channels:history. It never read channel messages; now it cannot.
  • After you remove Asyncbot, everything it stored about your workspace is deleted 14 days later, backups included. It used to be 30 days.
  • The “Edit existing” button on the duplicate-name message opens that rotation. It used to say the rotation did not exist.
  • Org-wide (Enterprise Grid) install is no longer offered. Install into one workspace at a time.

2.5.2 - 2026-08-27

  • The start date field now hides when scheduling is locked at the plan limit.

2.5.1 - 2026-08-27

  • A start date now requires a channel and time.

2.5.0 - 2026-08-27

  • Added an optional start date when creating a rotation, and on Edit for an existing rotation that has not had its first scheduled post. Leave it blank and nothing changes; pick a date and the rotation waits — nobody is on it yet, the card says when it starts, and the first scheduled day on or after that date activates the first person. Dates are read in the rotation’s own timezone. After the first post the field hides; you cannot put an already-running rotation back into pending.
  • Fixed the first scheduled post skipping the first person. Rotations used to advance before their very first post, so member two went first; now the first post belongs to the person shown on the card, and only later posts rotate.

2.4.1 - 2026-07-31

  • Fixed boot migrations erasing valid post-baseline history and crashing later deploys when an already-applied column was replayed.

2.4.0 - 2026-07-31

  • Three days after installing, a workspace gets one personal DM from Sven asking how it’s going — once per workspace, ever, and always during that workspace’s own working morning. What it says depends on what the workspace actually did: rotation posting, rotation set up but never posted, or no rotation yet.
  • Every check-in posts a receipt in the operator channel the moment it goes out, so a send is visible without waiting for a reply.
  • Fixed replies inside a bot-authored DM thread being silently dropped instead of reaching the feedback inbox.

2.3.0 - 2026-06-10

  • Added an advance webhook so you can advance a rotation from any tool (a scheduler, CI, another app). Workspace admins generate a private URL from a rotation’s ⋮ menu; the token is shown once and revocable. Retried or duplicate calls never skip or double-advance anyone.
  • Added “Advance & post” and “Post” buttons on the rotation card — hand off to the next person and announce in the channel in one click.
  • Fixed on-duty DMs silently dropping the guide button and handoff notes.
  • Every deploy now reports its version, commit, and build date on the health endpoint, and every push to production gets a release tag.

2.2.0 - 2026-04-13

  • Added a guide URL on rotations so people can jump straight to on-call documentation.
  • Added a footer to the daily summary for short standing links and reminders.
  • Polished the feedback flow: hid the quick rating after the first response and removed a stale thread hint.

2.1.0 - 2026-04-07

  • Added a customer feedback inbox with /async feedback, threaded operator follow-up, status tracking, stale reminders, and optional ratings.
  • Added date-based news items in daily summaries so short product updates can ride along with the daily post until they expire.
  • Hardened HiBob time-off sync with safer webhook handling, reconciliation repairs, open-ended leave support, and more robust setup validation.

2.0.0 - 2026-02-24

  • Added on-call handoff notes so the next person in rotation can pick up context cleanly.
  • Added HiBob time-off sync so approved leave can flow into Asyncbot availability.
  • Added stronger admin guards around Slack actions and workspace settings.