Skip to main content
What you need to knowSince BLAST automatically runs tasks concurrently, the only thing you may need to set is constraints:

Task Lifecycle

Every task in BLAST goes through several stages:
  1. Creation: Task is scheduled and assigned a unique ID
  2. Resource Allocation: Browser and other resources are assigned
  3. Execution: Task runs and streams progress updates
  4. Completion: Results are stored and resources are freed

Task Relationships

BLAST supports two types of task relationships:

Prerequisites

Tasks can depend on other tasks completing first:

Parent/Child Tasks

Tasks can spawn subtasks that run concurrently:

Task Priorities

BLAST prioritizes tasks in this order:
  1. Tasks with cached results
  2. Tasks with cached execution plans
  3. Subtasks of running tasks
  4. Tasks with paused executors
  5. Remaining tasks (FIFO order)

Concurrent Execution

BLAST can execute multiple tasks concurrently when resources allow:

Resource Management

BLAST automatically manages resources for concurrent tasks:
  • Limits concurrent browser instances
  • Reuses browsers when possible
  • Manages memory usage
  • Handles cleanup on task completion
Monitor resource usage:

Task State Management

Track task states through the API:

Next Steps