The Bot You Archived Kept Working Anyway

When you archive a bot in Nia, the expectation is simple: it stops. That's the entire point of the button — put it away, stop thinking about it.

Archiving hides a bot from the roster you see day to day. It does not stop any recurring schedule that bot owns — those keep firing exactly as they did before. That's actually a deliberate choice, not an oversight: archiving is meant to declutter what you look at, not silently cancel a schedule you set up on purpose and might still want. The problem was that nothing ever told you it was still happening.

The real case that surfaced this: a bot got archived, and a daily job it owned kept running on schedule and kept posting its results into a thread the archived view no longer shows you. Not for one day. For as long as nobody happened to go looking for it.

Working exactly as designed and being genuinely invisible turned out to be the same experience.

The fix isn't changing what archiving does — that behavior is intentional and stays. It's making sure you can't lose track of it. Archiving a bot now tells you, right there, exactly which schedules are still running underneath it and gives you a direct way to pause or delete each one. The job list itself flags any entry that belongs to an archived bot, so it shows up even if you never revisit that specific archive message again.

A deliberate design decision only actually holds up if the person it affects can see it happening. An intentional behavior that's also an invisible one isn't a feature — it's a trap that happens to be on purpose.