Skip to content
Projects and results

Understand tasks running in the background

Longer Agent Chat and project tasks continue on the server after you leave the page. Most finish sooner, but a project-research worker has a maximum execution window of about one hour before the run needs attention.

Reviewed August 30, 2026

What happens after you send a request

  1. Pelayar validates the request, attachments, selected tools, and project access.
  2. The request is placed in a durable queue and the progress card appears in the conversation.
  3. A worker prepares files, gathers evidence, runs the selected analysis, and saves progress as it goes.
  4. The worker publishes the answer, report, citations, or generated files back to the same conversation.

The work is tied to the conversation on the server, not to the browser tab. You can navigate to another page, close the tab, or refresh and return to the same conversation later.

Read the progress card

  • Queued: the request is waiting for a worker.
  • In progress: Pelayar shows the current phase, such as understanding the request, reading project evidence, gathering web sources, reviewing media, or preparing the final result.
  • Paused: some artifact work waits for a cost approval or another safe continuation step. Follow the action shown on the card.
  • Completed: the final response and any report or artifact actions are available in the conversation.
  • Needs attention: the run stopped before completion. The card shows a support reference when one is available.

Time limits

Background processing is bounded so a worker cannot run indefinitely. A project-research worker has a maximum execution window of about one hour (60 minutes) for a single research session. This is a safety ceiling, not a target wait time; most requests finish well before it.

General Agent Chat coordination, video indexing, Transcription, Video Analysis, Sports Analysis, and artifact generation can have different limits. Use the status and guidance shown by the selected workflow as the authoritative limit for that task.

If a task reaches its limit

  1. Return to the same conversation and refresh once to load the final status.
  2. Read the failure or needs-attention message and copy its support reference.
  3. Try a narrower request, fewer files, or a shorter media segment so the work fits within the available window.
  4. Use Retry or Continue only when the progress card offers that action. Otherwise, start one new request after confirming the first run has stopped.
  5. Contact Pelayar support with the conversation reference, project name, approximate start time, and last visible phase.

If progress appears stuck

Wait for the current phase to change before taking action. Refreshing does not restart an active run, but submitting the same request again can create duplicate work or additional processing charges.

If a file was already uploaded to a project, it normally remains available even when one analysis run fails. You can ask a smaller follow-up question from the same project after the failed run is closed. See Troubleshoot a stuck or failed task and Open and download reports and outputs.