Skip to main content

Documentation Index

Fetch the complete documentation index at: https://webscraping.titannet.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

This guide shows how to inspect execution state, list historical runs, and control runtime behavior where supported.

Execution monitoring flow

Inspect a single execution

Use:
GET /api/v1/executions/:id
This endpoint answers the most important runtime questions:
  • Did the execution start
  • Is it still running
  • What phase is it in
  • Did it complete successfully
  • Is result data ready yet

Execution statuses

StatusMeaning
queuedExecution exists but work has not started yet
runningWork is actively being processed
pausedExecution is paused
completedExecution finished successfully
failedExecution finished with an error
cancelledExecution was stopped before completion

List executions

Use:
GET /api/v1/executions
GET /api/v1/tasks/:id/executions
These list endpoints are useful for:
  • Dashboards
  • Polling workers
  • Admin tooling
  • Historical run inspection

Control a running execution

Task Service supports explicit runtime control actions:
ActionEndpoint
PausePOST /api/v1/executions/:id/pause
ResumePOST /api/v1/executions/:id/resume
StopPOST /api/v1/executions/:id/stop
These are runtime operations, not task definition updates.
async function pollExecution(executionId: string): Promise<any> {
  const terminalStatuses = ["completed", "completed_with_errors", "failed", "cancelled"];
  while (true) {
    const exec = await titanRequest("GET", `/executions/${executionId}`);
    if (terminalStatuses.includes(exec.status)) return exec;
    await new Promise((r) => setTimeout(r, 3000));
  }
}

What to do after completion

Once an execution reaches completed, switch from execution APIs to:
  • Result metadata endpoints
  • Export endpoints
  • Dataset endpoints
  • Media download endpoints
That separation keeps runtime logic and output consumption clean.

Troubleshooting

ProblemCheck first
Execution never leaves queuedWorker capacity and scheduler health
Execution flips between states unexpectedlyVerify whether pause/resume logic is in use
Execution is completed but exports failResult ingestion or result path timing
Execution is failedInspect execution details and platform logs

Next steps