Vigie
Features

Tasks

Every attempt of every background job, why it failed, skipped or will retry, and what is stuck.

The Tasks screen answers three questions in order: is work flowing, is it succeeding, and are the workers alive.

  • Flow. How many tasks are due, how long the oldest has waited, and which kinds run late. Fed by the vigie.tasks.backlog and vigie.tasks.oldest_due_age gauges, and by lateAfterSeconds in your catalog.
  • Execution. Failure rate per kind, the codes behind failures, and every skip and retry with its reason.
  • Liveness. Which workers reported recently, and attempts that started but never finished because their worker died.

Each run has its own page: every attempt, its outcome, the trace of each try, the queries and external calls it made, and, when your app's database is connected, the row as it is now.

Sending tasks

FromHow
Adonistask()
NestJS@VigieTask()
Anything elseA wide event with task.kind and taskOutcome.type. See the contract.

Acting on tasks

With VIGIE_APP_API_URL set, the run page offers Requeue, Cancel and Run now. Vigie calls your app's API as the person who clicked, so your app keeps the permission checks. Agents with a write token can do the same with requeue_task, cancel_task and bulk_task_action.

With VIGIE_APP_DATABASE_URL set to a read-only role, Vigie reads queued tasks straight from your app's database. See Configuration.

Copyright © 2026