Layers

Layer Detail Page

Per-layer settings, commands, runs, and billing.

View as Markdown

Click any installed layer to open its detail page at /project/{projectId}/layers/{layerId}. The page has tabs.

What you see

Each layer's detail page shows (depending on the template):

  • Layer-specific settings (rendered by the template's settings form).
  • Executable commands that can be run on demand.
  • A history of recent workflow runs triggered by this layer.
  • Status and any connection-health indicators for linked external resources (ad accounts, social accounts, API keys).

Settings

Each template renders its own settings UI. Common controls:

  • Mode toggle (manual vs automatic / custom).
  • Cron override (via config.schedule.cron).
  • Template-specific inputs (budgets, distribution rules, connected accounts).

See per-template guides:

Commands

Each template defines a set of commands (declared in its commands map). Executable commands are triggered via the layer execute API (POST /api/project-layers/:id/execute). Scheduled commands fire automatically on their configured cron.

Runs

Each workflow triggered for this layer writes a workflow run. Status values are running, completed, failed, and canceled. Runs include a workflow run ID you can share with support when debugging.

Pause / remove

Pausing / removing a layer is surfaced in the app's layer-management UI (the exact control varies by template). When a layer is paused or soft-deleted (is_active = false / is_deleted = true), the scheduler tick filters it out and its *-scheduled commands stop firing. Existing in-flight workflows finish normally; no new ones start.

On this page