Skip to main content

Console Log

Category: User Interface Console Log block screenshot

Writes the evaluated value to the Automation Agent console for diagnostics and user feedback. Messages beginning with `PROGRESS|` can additionally update the non-blocking current-run label in compatible Panel and MCP interfaces. A final `SUMMARY|workflow=<stable-id>|...|timingReport=<path>` message can remain visible as a non-modal completion summary in compatible Panels when the overall run succeeds. Use the workflow-neutral structured forms documented below for reusable long-running workflows; older interfaces retain them as ordinary console messages.

Inputs​

InputRequiredValue KindTypesEnum Values
messageyesexpressionstring, number, boolean, reference, array—

Notes​

  • Writes the evaluated message to the ordinary Automation Agent run log.

  • A single-line message beginning with PROGRESS| is additionally interpreted as a non-blocking current-status update by compatible Panel and MCP interfaces. It remains an ordinary console line as well, so older versions degrade safely without failing the script.

  • The recommended workflow-neutral form is:

    PROGRESS|workflow=<stable-id>|phase=<phase>|current=<number>|total=<number>|unit=<singular-label>

    For example, PROGRESS|workflow=archive-deliverables|phase=ENCODE|current=3|total=12|unit=file is displayed as Encode · File 3/12.

  • workflow is a stable machine-readable workflow identifier. phase is the preferred current phase; stage is accepted as a compatibility alias. current, total, and unit describe generic bounded work. Omit fields that are not known rather than inventing totals.

  • Existing specialized counters remain supported for compatibility: source with sources or totalSources, chunk with chunks or totalChunks, shot with shots or total, batch with batches, and firstShot with lastShot.

  • Keys are case-sensitive. Values should be short, single-line values and must not contain |. Unknown fields are ignored by the status formatter but remain visible in the console record.

  • Each recognized PROGRESS| line replaces the displayed current status; it is not a durable completion report.

  • A single-line message beginning with SUMMARY| remains ordinary console output and can additionally become a persistent, non-modal completion summary in compatible Panel interfaces. It is displayed only when the overall run completes successfully; a later failure, cancellation, or blocked run clears the pending summary. This makes it safe to emit the record as the final successful workflow statement without holding unattended or MCP-initiated runs open in a dialog.

  • Use SUMMARY|workflow=<stable-id> followed by short scalar result fields. Put a human-readable timing file in timingReport=<path> when one exists; compatible Panels prioritize that path in the visible completion text. report=<path> and result=<path> are fallback report fields. For example:

    SUMMARY|workflow=archive-deliverables|files=12|timingReport=/reports/archive-times.txt

    Older interfaces retain the complete line in the console and otherwise ignore it, so the convention is backward-compatible. SUMMARY| is a discovery aid, not a replacement for the durable report itself.

  • Status delivery happens only after the esConsoleLog block executes and the runtime/UI can observe the log. It does not stream from inside a currently blocking runExternalProgram, Premiere host call, dialog, or other atomic operation. Emit updates at honest bounded-unit boundaries; do not imply finer-grained progress than the program can actually observe.

Examples​

Structured Workflow AI Extract Text Fields

Calls the configured Workflow AI provider with a small JSON Schema, stores canonical JSON text, projects top-level fields into variables, and records run-scoped diagnostic artifact paths without mutating Premiere.

kind: Pattern · format: runtime-dsl · validation: Schema only

Topics: workflow ai, askAgent, structured output, json schema, field projection

Source: patterns/ex-workflow-ai-structured-extract-text-fields.json

Download JSON

Apply One Audio Effect On An Isolated Sequence

Creates a fresh sequence from one source item, applies one audio effect to the first audio clip, and verifies that the component count increases by one.

kind: Pattern · format: runtime-dsl · validation: MCP fixture

Topics: effects and component parameters, audio

Source: patterns/ex-audio-effect-apply-on-isolated-sequence.json

Download JSON

Apply One Video Effect On An Isolated Sequence

Creates a fresh sequence from one source item, applies one video effect to the first clip, and verifies that the component count increases by one.

kind: Pattern · format: runtime-dsl · validation: MCP fixture

Topics: effects and component parameters, track item mutation

Source: patterns/ex-video-effect-apply-on-isolated-sequence.json

Download JSON