All Broadcasts Status
One screen → active, stuck, and pending sends
In short
Campaign statuses are scattered across channels, so a stuck worker or overdue confirmation can go unnoticed for hours.
Outcome
A read-only summary shows active campaigns, actual progress, lost workers, pending confirmations, and recent results across all channels.
How the automation runs
Trigger
Operator opens summary or monitor initiates scheduled check
Automation steps
- Reads campaign states and actual delivery logs
- Compares active state with the presence of a live worker
- Highlights overdue approvals and progress discrepancies
- Sends an alert based on a confirmed 'stuck' rule
- Shows recent completions and cancellations without control actions
Human check
The interface only reads and does not launch, confirm, or resume campaigns; an automatic watchdog can only safely close a demonstrably lost run and call a person.
Outcome
A read-only summary shows active campaigns, actual progress, lost workers, pending confirmations, and recent results across all channels.
Automation diagram
The overall logic is publicUsing it
When to use it
Broadcasts are sent through multiple channels, and status needs to be checked more often than manually verifying processes and tables.
How to verify
The summary matches a control verification of logs, a test lost worker is detected within the specified time, and it's impossible to start sending from the interface.
Tools
Recipe details
Open every recipe through @venturehunter
We ask for no phone number, no password and no Telegram login on the site. @penioza_bot checks your subscription inside Telegram and brings you back here with access to every kit, not just this one recipe.
Need help putting this in place?
We will walk through your process and build this loop around your data, your limits and your people.
Message me — I will help
