Task Queue — how this works

In the app: /tasks

How it works

The manual steps of a cadence (call / LinkedIn / generic task) surface here as due work, alongside any ad-hoc task — the cadence walker creates one Task per manual step when it comes due. Each row shows the lead's context and a Complete / Skip action; completing or skipping a task just updates its status, it doesn't fire anything outward.

Data source

src/lib/cadence/taskRepo.ts (Task model). Manual cadence steps are turned into tasks by the walker (src/lib/cadence/walker.ts) via cadenceTaskHandler.

Troubleshooting

Expected a task that isn't here? The queue shows only PENDING tasks whose dueAt has passed — a future-dated step won't appear until it's due, and a completed/skipped one drops off. Manual cadence steps only become tasks once the walker cron is running against due enrollments.

Who can see this: admin, closer, setter