Automation Queue

The Automation Queue at /jobs shows every background job Ru and your automations have run: brief analyses, background Ru tasks such as brand asset generation and scheduled automation runs, image and video generation, and historical agent jobs. Use it to check progress, inspect failures, and get back to results.

What the page shows

At the top, summary tiles count your Active, Completed, and Failed jobs for the current view. Below them, the queue lists each job with its type, status, and when it ran.

A job is always in one of five states: Pending (queued, not started), Processing (running now), Completed, Failed, or Cancelled.

Turn on Auto refresh in the page header to keep the queue updating while jobs run.

Filter and change the layout

• Status filters: choose All, Active (pending and processing), Completed, or Failed to narrow the list.
• List or Cards: switch between a compact list and a card layout with the toggle beside the filters. Your choice is remembered in your browser, so the queue opens in your preferred layout next time.

Act on a job

Each job offers the actions that make sense for its state:

• Open Chat on an interactive session returns you to that conversation.
• View Results on a completed job opens the job’s output.
• Cancel stops a pending or processing job.
• Retry re-runs a failed job.

Jobs from the retired AI agent catalogue stay viewable, but retrying one fails with a message explaining that the work now runs through Ru. Ask Ru for that work instead; see AI Directives.

When a job you started finishes or fails, you are also notified; see Messages & Notifications for how completion and failure notifications link back to results and this queue.

Understand a failed background task

The queue shows the recorded failure reason in both List and Cards views. Choose Open Chat on a background Ru task to see its read-only transcript. New runs record the tools they start and whether each completed or failed. These updates remain available after you leave the page and return.

If a run failed, its explanation appears in the transcript. Older runs may show an expanded Failure details section with the stored reason. Review any saved files before starting again, because work completed before a failure is retained.

A website fetch timeout or web service failure means research could not retrieve the page. It does not mean the address is private. Ru can use other available sources and must identify gaps in the evidence.

Next steps

Learn how directive playbooks steer background work in AI Directives, or start a conversation with the Chat Assistant.

Older brief planning results can open a separate Resource Plan page. See review a saved brief plan for its editing controls and live-project lock.