Repository navigation
Activity Accept Event Action Node
An Accept Event Action Node waits for an incoming event of a declared type. When that event is delivered while the node is active, its action runs and its outgoing flows can continue the Activity. It models an event-accepting action in UML; the event itself is not an object-flow token.
Register the event type and optional callback with AddAcceptEventAction<TEvent>. The callback can inspect c.Event; the node can also receive ordinary tokens through incoming object flows.
public sealed record PaymentCaptured(string PaymentId, decimal Amount);The following fragment belongs inside the relevant method or builder callback:
.AddInitial(node => node.AddControlFlow("AcceptPayment"))
.AddAcceptEventAction<PaymentCaptured>(
"AcceptPayment",
async c => await payments.RecordCaptureAsync(
c.Event.PaymentId, c.Event.Amount, c.CancellationToken),
node => node.AddControlFlow("IssueReceipt"))
.AddAction(
"IssueReceipt",
async c => await receipts.IssueAsync(
c.CancellationToken),
node => node.AddControlFlow<FinalNode>())
.AddFinal()The event action is eligible only while its node is active. A later event is not consumed once the modeled execution has ended or the node is no longer active. Multiple event types can be handled by separate event-accepting nodes; the OneOf extension can combine alternatives where appropriate. See Send Event Action Node, Time Event Action Node, and Activities.
When the event is defined in Stateflows' structural event registry rather than as a CLR event class, use the overload that takes its registered event name. Its callback receives a StructuralEvent, whose values are read by field name:
using Stateflows.Common;
using Stateflows.Events;
// Register this definition during Stateflows configuration:
builder.AddEvents(events => events
.AddEvent("payment-captured", e => e
.AddField("paymentId", FieldType.String)
.AddField("amount", FieldType.Decimal)));
// In the Activity definition:
.AddAcceptEventAction(
"payment-captured",
"AcceptPayment",
async c => await payments.RecordCaptureAsync(
c.Event.Get<string>("paymentId"),
c.Event.Get<decimal>("amount"),
c.CancellationToken),
node => node.AddControlFlow("IssueReceipt"))This is different from AddAcceptEventAction<TEvent>: the string overload matches the registered structural event name, and the callback receives StructuralEvent, not a CLR class. Structural definitions and IEventFactory creation are described in Events.
Home page Support Code licensed under an MIT-style License. Documentation licensed under CC BY 4.0. © by Mikołaj Milewski, 2026
Overview
Installation
Runtimes
Orleans runtime
Concepts
Events and Structural Events
Messaging Patterns
Validation
Scheduling
Observability
Behaviors
Behavior Values
Dependency Injection
Behavioral Groups
State Machines
Concepts
State Identity
In-State Event Deferrals
Evaluation of Transitions
Exception Handling
Building blocks
Regions
States
State
Composite State
Orthogonal State
Final State
Pseudostates
Choice
Junction
Fork
Join
History
Transitions
Transition
Default Transition
Internal Transition
Activities
Concepts
Exception Handling
Implicit Fork and Join
Tokens
Building blocks
Nodes
Action Node
Decision Node
Merge Node
Initial Node
Final Node
Input Node
Output Node
Fork Node
Join Node
Accept Event Action Node
Send Event Action Node
Publish Event Action Node
Time Event Action Node
Data Store Node
Structured Activity Node
Iterative Activity Node
Parallel Activity Node
Flows
Data Flow
Control Flow
Actions
Entities
Fields
Mutations
Projections
Extensions
ClearScript
FluentValidation
JSON definitions
Minimal APIs
OneOf
OpenTelemetry
PlantUML
Scheduling