Surface stalled courses before they go stale
Every morning, WebRun opens Cognota, finds active projects with no stage change or task activity beyond your stall threshold, works out the likely blocker for each, and posts a Slack list of stalled courses ranked by how long they have been idle, so stuck work gets unstuck.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find learning projects that have stalled with no activity?
WebRun scans active Cognota projects every morning for ones with no stage change or task activity past your stall threshold, reads each project's stage to infer the blocker, and posts a Slack list ranked by days idle with the owner and likely reason. It changes nothing itself, so unblocking stays your call while stalled work stops hiding.
- Idle projects surface within a day of going quiet
- Each stalled course arrives with a likely reason, not just a name
- The oldest stalls are ranked first so nothing rots for weeks
Built for L&D managers · instructional design leads · learning operations teams · training program managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.cognota.comin a real browser with your saved login - no setup, no API keys. -
1
Cognota - find idle projects
cognota.com How to Automate Cognota
WebRun opens Cognota to find idle projects. - Open Cognota and list active projects with their last activity date
- Flag any project with no stage change or task update beyond your stall threshold, for example 7 days
- For each, read the current stage and open task to infer the likely blocker
- Capture the project owner and how many days it has been idle
Done when Every idle project past the threshold is listed with its owner, stage, and likely blocker.
-
2
Slack - surface stalled courses
slack.com How to Automate Slack
WebRun opens Slack to surface stalled courses. - Post a stalled-work list to the internal L&D Slack channel
- Rank projects by days idle, longest first, with the owner noted
- Note the current stage and likely blocker for each so the fix is obvious
- Frame each line as something to unblock, not an automatic action taken
Done when The team has a ranked Slack list of stalled courses and why each is stuck.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change anything in Cognota?
No. It only reads project activity and posts a Slack list. Reopening, reassigning, or closing a stalled project stays a human decision, so nothing in Cognota is touched automatically.
How long is idle before a project counts as stalled?
You set the threshold, for example 7 days with no stage change or task activity. WebRun uses that window each morning, so the list matches how your team defines a stalled project.
How does it guess why a project is stuck?
It reads the current stage and the open task in Cognota, so a project idle in review reads as waiting on a reviewer while one idle in design reads as waiting on a designer, giving each line an actionable reason.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.