Monitoring
Once a workflow is live, the question changes from "will it work?" to "did it work?" Juno answers with receipts: every run, message, event, and scheduled firing leaves a record you can inspect from the workflow's activity view — so you debug from evidence, not from scrolling Discord.
The activity view
Open a workflow's activity and you get the recent story: runs and their outcomes, interactions handled, events sent and received, scheduled firings, and the Discord actions performed. Filter by time range, and follow any entry to the related ones — from the trigger, to the run, to everything that run caused, across workflows. When a member says "the bot ignored me," you can find that exact moment and see what actually happened.
Healthy, retrying, or stuck
Most operations either succeed or retry automatically. What deserves your attention is the small set that ends up stuck — something failed repeatedly and Juno has parked it, with its error message, instead of retrying forever or losing it silently:
- A message that could not be delivered to a listener.
- A Discord action that kept failing — often a permissions change or a deleted channel.
Stuck items are your to-do list. Each one names what failed and why; the fix is usually restoring a permission, re-pointing a setting at a channel that still exists, or publishing a repaired version.
When Discord wobbles
Talking to Discord is the least predictable part of any workflow, so Discord actions get the most detailed accounting. Beyond success and retry, you may occasionally see an action marked as uncertain — Discord went quiet at exactly the wrong moment, and Juno can't prove whether the action landed. Rather than guess (and risk doing it twice), it's flagged for you to eyeball. A partially-completed multi-step action is likewise recorded as such, not rounded up to "fine."
This honesty is deliberate: the activity view tells you what Juno knows, and says so when it doesn't know.
A publish-day habit
After each publish, give the activity view one look: trigger something yourself, watch the run appear, confirm it succeeded. Sixty seconds. Most broken deployments announce themselves in the first handful of runs — usually as a permission the bot lost or a setting that no longer points anywhere.
Deleting with receipts
When you retire a workflow for good, Juno runs the same evidence through a safety check and shows you what still exists before anything is removed: remembered values it accumulated, schedules still active, work still in flight, other workflows that depend on it, and any Discord artifacts (like channels it created) that you'd need to clean up by hand. If something still depends on the workflow, deletion is blocked with the reason named. Nothing disappears while the evidence says it's still alive.