Mixed freshness. Depending on the panel, rows here are read live from elisa-core or come from a frozen copy of ELISA’s local store taken on 22 October 2026 — each panel says which, underneath itself. No agent is running.

ELISA
Connecting

Execution Log

Who triggered a run, which agent executed it, which tools were called, the approval used, and what came back.

Nothing here yet

Agent is not connected. No agent runtime is attached to this install yet, so nothing can be queued, run or executed.

Once a runtime is attached, this page will show one row per tool call, who triggered it, the approval it ran under, and the result..

Per-execution fields

ExecutionRecord in lib/erp/records.ts — the contract, not a sample row.

idstring
jobIdstring
toolNamestring
approvalIdstring | null
result'success' | 'failed' | 'partial'
externalIdstring | null
errorCodestring | null
startedAtstring
finishedAtstring | null

Observability contract

D:\ELISA\ELISA_CONNECTORS_AUTONOMY.md §9 — what every run will expose, once a runtime exists.

  • who triggered it
  • which orchestrator routed it
  • which agent executed it
  • input record IDs
  • tools called
  • approval status
  • output record IDs
  • latency and token/cost estimate
  • retries and errors
  • final recommendation
  • feedback and learning status