Skip to main content

Catch Blocked and Stale Tasks Automatically

By the end of this recipe, no task will quietly rot in your board — the moment something goes overdue, gets blocked, or falls silent, Copera nudges the person who owns it with a specific message about what's stuck and what's needed next. Because your tasks and your team chat live in one workspace, the detector can spot the stuck row and reach the right person directly, instead of waiting for someone to notice in a status meeting.

Readiness: Available now (built as two Automations). The version where a named teammate watches every board and nudges owners on its own is rolling out in early access.

What it does​

Work doesn't usually stall with a dramatic announcement. It stalls quietly: a due date slips past, a task gets flagged "Blocked" and then sits, or an item just goes silent for a week while everyone assumes someone else has it. This recipe makes all three impossible to miss.

The detector watches your task board for three signals you define:

  • Overdue — the due date has passed and the task still isn't Done.
  • Blocked — the status is set to Blocked, so it's waiting on something.
  • Stale — no comment or update for a number of days you choose (say, seven), even if it isn't technically late yet.

When a task trips one of those signals, the detector drafts a short, specific nudge — the task name, why it's flagged ("overdue by 3 days," "blocked since Tuesday"), and what's needed to move it — and direct-messages the owner. Newly blocked work can also alert the manager instantly, so a blocker gets a second set of hands the moment it appears rather than at the next standup.

Done and cancelled tasks are skipped, so no one is ever nudged about finished work.

Build it yourself​

Two small automations do the whole job: a morning sweep that catches everything already stuck, and an instant alert the moment a task gets blocked. Both live in Automations.

Before you start​

On your task board, make sure each row has the fields the detector reads:

  • A Status field with a Blocked option and a Done option (plus whatever else your team uses).
  • A Due date field.
  • An assigned owner (a people column) — this is who gets nudged.

That's the whole setup. See Boards Overview if you're building the board from scratch.

Automation 1 — the daily stuck-work sweep​

Trigger: Schedule

Add a Schedule trigger set to when your team starts the day — for example, every weekday at 8:30 AM. This is the sweep that catches everything currently stuck.

Action: Find rows

Add a Find rows action on the task table that returns the stuck work: Status is not Done or Cancelled, and either the Due date is before today or the Status is Blocked. This is the same filtering you already use on views, so you can tune exactly what counts as stuck.

Control: For each

Add a For each step over the rows that came back, so the following steps run once per stuck task.

AI step: Draft the nudge

Inside the loop, add an AI → Generate step that writes a short, specific message from the task's fields — its name, whether it's overdue or blocked, how long it's been that way, and a suggested next step. Prompt it for tone: "Write a brief, friendly nudge the owner can act on in a minute."

Action: Nudge the owner

Add a Send direct message action to the task's owner, including the drafted nudge and a link to the row: "⏰ 'Launch checklist' is 3 days overdue — here's what's left." Prefer a lighter touch? Swap in a Send notification for an in-app ping instead of a DM.

tip

Also flag it on the board. Add a Set field action in the loop to mark each stuck row "Needs attention," so anyone scanning the board sees the same signal the owner just got in their DMs.

Automation 2 — the instant blocked alert​

The sweep catches blockers once a day. This second automation escalates them the instant they appear.

Trigger: Field changed

On the same board, add an automation with a Field changed trigger watching the Status column.

Condition: Changed to Blocked

Add a condition that only continues when the status changed to Blocked (a changed from → to check). This keeps the alert firing only on new blockers, not every status edit.

Action: Alert the lead

Add a Send direct message (or Send notification) to the task's manager or team lead: "🚧 'Payment webhook' was just marked Blocked." Add a Post channel message to your standup channel too, if the whole team should see blockers as they land.

Optional: Start an SLA timer

Add an SLA timer control action to start a timer when a task is blocked. If it stays blocked past your threshold, an SLA breach can trigger a follow-up automation that escalates further.

tip

Catch the truly quiet ones, too. Overdue and blocked are easy to spot; a task that's simply gone silent is trickier. Add a third automation with a Date reached trigger set to the "N days after last comment" option (say, 7 days), with a condition that the status isn't Done — then nudge the owner. It's the same detector, aimed at work that stalled without ever looking late.

Or just ask Copera AI​

Want the state of play right now, without building anything? Open Ask Copera AI and ask:

"Look at our Tasks board and find every task that's overdue or marked Blocked and isn't done yet. For each one, tell me who owns it and how long it's been stuck, then DM each owner a short nudge with the task name and what's needed to move it forward."

Ask Copera AI reads the board, finds the stuck work, and drafts the nudges on the spot — a fast way to triage on a Monday without waiting for the scheduled sweep. Because it acts under your default Ask before acting permission mode, it shows you each direct message on a review card before it sends, so you approve exactly what goes out. See What Copera AI Can Do for the full set of actions it can take.

Make it a standing teammate​

Early access

Standing AI teammates are rolling out gradually. When one reaches your workspace, a named teammate can own this beat across every board: watch for overdue, blocked, and stale work, draft the nudge for each one, DM the owner, and flag new blockers to the lead — on its own schedule and under its own identity. Until then, the two automations above do exactly this today. Everything in this guide can be built now as an Automation.

Tips​

tip

Send one digest, not a flood. If DMing every owner feels noisy, add an AI → Summarize step after Find rows and a Post channel message action to drop a single "here's what's stuck today" digest into your standup channel. Owners still get their individual nudges; the manager gets the whole picture in one message — and it feeds naturally into a weekly status digest.

tip

Tune the thresholds to the team. A design task quiet for two days isn't the same as a compliance task quiet for two days. Duplicate the stale-check automation with a tighter window for high-stakes tables, so the work that matters most gets chased first.

tip

Keep the human in the loop on anything external. This recipe nudges your own people by default, so it's safe to run automatically. If you extend it to email a client or vendor about a delay, use a draft or approval delivery step so a person signs off before it leaves the workspace.

tip

Set a spend cap. Because the sweep drafts a message per stuck task in a loop, give the automation a per-automation spend cap so a chaotic week can never run past a budget you choose. The usage dashboard shows exactly where credits go.

Frequently Asked Questions​

How does Copera find blocked and stale tasks?​

It watches your task board on signals you define. A scheduled Find rows sweep returns every task that's overdue or marked Blocked and still open, and a Date reached trigger can fire a set number of days after the last comment for work that's gone quiet. Each stuck task then nudges the person who owns it.

Does it nudge the task owner or the manager?​

By default it direct-messages the assignee who owns the task with a specific, ready-to-act nudge. A second automation alerts the manager the moment a task is marked Blocked, so someone can help unblock it right away instead of waiting for the next status meeting.

What counts as a stale task?​

You decide. A task is overdue when its due date has passed and it isn't Done, blocked when its status is Blocked, and stale when there's been no comment or update for a number of days you set, such as seven. Done and cancelled rows are always skipped.

Does the AI write the nudge message?​

Yes. An AI → Generate step drafts a short, specific message from the task's context — its name, why it's flagged, and what's needed next — so the owner gets a useful nudge instead of a generic reminder. Send it as a direct message or a lighter in-app notification.

Can I get one digest of everything stuck instead of many DMs?​

Yes. Add an AI → Summarize step over the found rows and a Post channel message action to post a single digest to your standup channel, so a manager sees all overdue and blocked work at a glance while owners still get their individual nudges.