elsa-core/doc/wiki
Sipke Schoorstra 952dfa05ff
feat(bpmn): project interpreter diagnostics onto the scope's execution log (#8058)
* feat(bpmn): project interpreter diagnostics onto the scope's execution log

Under Option A only bound work carries an activity id, so gateways, events and
flows had no per-element trace in the journal. BpmnScopeHost now projects each
new BpmnExecutionState.Diagnostics entry onto the scope's own execution log
before Prune() runs, keyed by element id, with a persisted high-water mark so
a resumed scope never re-emits one. The scope's own start and completion stay
out, since they are already journaled as the activity's own lifecycle. Event
names and the payload shape are documented as a public compatibility surface
for elsa-studio#1000 to mirror.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(bpmn): project element and flow diagnostics dropped by the FlowId exclusion

The diagnostics exclusion keyed on Kind == TokenEmitted && FlowId is null/empty
also dropped an error or cancel boundary's own token emission, since a
boundary fires without an inbound flow. Narrow the rule to skip only
diagnostics that name neither an element nor a flow -- the scope's own
terminal Completed summary -- so every diagnostic keyed on an element or a
flow, including a start event's and a boundary's, is projected.

Also make DiagnosticSequence resilient: TryParse instead of Parse, logging a
warning and skipping projection for an id that doesn't match diag:N rather
than faulting the evaluation. Add a reflection-based test that keeps
BpmnDiagnosticEventNames in lockstep with BpmnDiagnosticKind, and record the
diagnostics volume measurement in the wiki.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(bpmn): require exact diag:N ids and seed the diagnostics cursor from prior state

Reject any diagnostic id that is not the exact "diag:" prefix followed by a
non-negative integer, so a malformed id can no longer poison the durable
projection cursor and cause later, genuinely valid, lower-sequence
diagnostics to be skipped forever.

Also seed a missing cursor from the highest valid sequence in the scope's
prior persisted state instead of treating it as zero, so a scope persisted
before diagnostics projection existed does not replay every retained
historical diagnostic as new on its next evaluation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-09-11 19:01:06 -07:00
..
activities-and-authoring.md Refresh codebase wiki (#7464) 2026-05-19 00:49:27 +02:00
architecture.md Add ingress rate limiting hooks (#7512) 2026-05-22 00:13:11 +02:00
bpmn-workflows.md feat(bpmn): project interpreter diagnostics onto the scope's execution log (#8058) 2026-09-11 19:01:06 -07:00
build-run-operate.md Add read-only workflow runtime status permission 2026-06-16 23:27:59 +02:00
diagnostics-console-logs.md Enhance console logging with improved context and lifecycle (#7536) 2026-05-27 00:14:28 +02:00
diagnostics-structured-logs.md Refresh codebase wiki (#7464) 2026-05-19 00:49:27 +02:00
expressions-and-scripting.md refactor(auth): remove the vestigial per-author script permission plumbing (#7990) 2026-08-25 22:58:16 +02:00
extension-guide.md Add ingress rate limiting hooks (#7512) 2026-05-22 00:13:11 +02:00
health-checks.md Address health check review feedback 2026-05-21 02:13:19 +02:00
http-scheduling-resilience.md docs(wiki): point the scheduling link at StartupTasks 2026-08-12 00:02:13 +02:00
identity-tenancy-security.md feat(auth)!: structured authorization model, phases 1-6 (#7980) 2026-08-24 23:44:55 +02:00
module-system.md fix(features): support features introduced during Module.Apply() (#7966) 2026-08-20 23:53:07 +02:00
opentelemetry-workflows.md [codex] Fix console log metadata and type resolution (#7542) 2026-05-30 22:52:01 +02:00
output-converters.md Add output converter support at binding boundaries 2026-07-31 04:10:48 +02:00
persistence.md Refresh codebase wiki 2026-08-11 22:25:06 +00:00
README.md Add output converter support at binding boundaries 2026-07-31 04:10:48 +02:00
repository-map.md Refresh codebase wiki (#7922) 2026-08-17 00:58:59 +02:00
specs-and-adrs.md Refresh codebase wiki (#7922) 2026-08-17 00:58:59 +02:00
testing-guide.md Refresh codebase wiki 2026-08-11 22:25:06 +00:00
workflow-api.md Refresh codebase wiki 2026-05-23 14:19:02 +00:00
workflow-core.md feat(core): let a container withdraw work it scheduled but must not run (#7967) 2026-08-20 23:29:46 +02:00
workflow-management.md
workflow-runtime.md Add read-only workflow runtime status permission 2026-06-16 23:27:59 +02:00

Elsa Core Wiki

This wiki is a repo-local, code-grounded map of Elsa Core. It is intended for contributors who need the same kind of fast orientation that a DeepWiki-style generated wiki gives: what the system is, where the important code lives, how the pieces connect, and how to safely extend or test them.

The source of truth is still the code, specs, ADRs, and tests. Each page links back to the relevant files so you can jump from explanation to implementation.

Start Here

Elsa Core is a modular .NET workflow engine. The main solution is Elsa.sln. Production code lives under src, tests under test, specifications under specs, and architecture decisions under doc/adr.

The shortest mental model:

  1. An application calls services.AddElsa(...).
  2. Elsa builds an IModule and configures feature objects.
  3. Features register services, activities, API endpoints, middleware, hosted services, and persistence stores.
  4. Workflow definitions are created by code, JSON, imported files, or providers.
  5. The runtime starts, resumes, dispatches, and persists workflow instances.
  6. APIs, SignalR hubs, HTTP endpoint activities, diagnostics, and persistence packages layer around that core.
flowchart LR
    App["Host app"] --> Module["Elsa module system"]
    Module --> Core["Workflow core"]
    Module --> Management["Workflow management"]
    Module --> Runtime["Workflow runtime"]
    Module --> Api["Workflow API"]
    Module --> Extensions["HTTP, Scheduling, Expressions, Identity, Tenants"]
    Management --> Persistence["Stores / EF Core providers"]
    Runtime --> Persistence
    Runtime --> Logs["Execution logs and diagnostics"]
    Api --> Studio["Elsa Studio / API clients"]

Page Map

Page Use it for
Repository Map Top-level folders, projects, and where to look first.
Architecture The main system layers and request/execution flow.
Module System How IModule, FeatureBase, feature dependencies, and shell features work.
Workflow Core Activities, execution contexts, pipelines, variables, bookmarks, graphs, and flowchart execution.
Workflow Management Workflow definitions, instances, import/export, materializers, validation, and activity descriptors.
Workflow Runtime Dispatch, triggers, bookmarks, queues, background activity scheduling, graceful shutdown, and recovery.
Workflow API FastEndpoints, route prefixing, API categories, SignalR, and client-facing contracts.
Activities And Authoring How workflows are authored in C#, JSON, ElsaScript, and host methods.
Output Converters How to register, configure, validate, discover, and operate bound-value converters.
Expressions And Scripting Expression evaluators and language feature packages.
HTTP, Scheduling, And Resilience Inbound HTTP workflows, outbound HTTP, scheduled triggers, and resilience strategies.
Persistence In-memory stores, EF Core stores, provider packages, migrations, and multi-provider rules.
Diagnostics Structured Logs ILogger capture, live feed, REST/SignalR surface, redaction, and SQLite persistence.
Diagnostics Console Logs Raw stdout/stderr capture, live feed, REST/SignalR surface, and redaction.
Health Checks Elsa runtime readiness probes, liveness/readiness mapping, and Kubernetes probe guidance.
Identity, Tenancy, And Security Users, applications, roles, API keys, tenant resolution, and authorization touch points.
Testing Guide Test project layout, fixture choices, and targeted commands.
Extension Guide How to add features, activities, expression providers, stores, endpoints, and ingress sources.
OpenTelemetry Workflow Instrumentation First-party workflow and activity traces and metrics emitted through System.Diagnostics.
Specs And ADRs How current specs and ADRs explain design intent.
Build, Run, And Operate Build commands, sample hosts, runtime knobs, Docker notes, and operational endpoints.

Source Landmarks

Contributor Workflow

Use targeted reads first, then targeted tests. For most changes, start with the relevant module page, inspect the linked feature class and contracts, add or update tests in the matching test/unit, test/integration, or test/component project, and run the narrowest dotnet test command that proves the behavior.

When changing public behavior, update the related README, spec quickstart, or wiki page in the same PR. This repository is strongly modular, so the best changes keep ownership boundaries clear.