PlatformEvents & exception coordinationExplore features

Connect

Respond when the business context changes.

Coordinate messages, deadlines, signals and errors with the work they affect. Make waiting behavior and exception responses explicit, including the human follow-up needed when the expected path cannot continue.

Native BPMN pools, responsibility lanes and a review loop. Unpublished demonstration draft.
Native BPMN pools, responsibility lanes and a review loop. Unpublished demonstration draft.

Inside the product

Follow the work, then inspect the detail.

Explore actual captured Inflow views. Change the view, open the original and read the context beside it.

Recorded inside Inflow · Fictional demonstration data · Original English UI2560 × 1440

Work inside a state

A message wait, a human document task and a decision gateway explain the work behind Awaiting documents. The side panel connects that flow to waiting cases.

Native execution view with fictional records. The November activity chart is empty because the demonstration cases were started in October.

Explore this capability

Original native capture

Work inside a state

A message wait, a human document task and a decision gateway explain the work behind Awaiting documents. The side panel connects that flow to waiting cases.

Native execution view with fictional records. The November activity chart is empty because the demonstration cases were started in October.

Open full resolution

The detail behind the capability.

Message-driven responses

A process may wait for a meaningful message. The retained event model uses supplier acknowledgement as a business-specific example.

Deadlines and timer routes

Make time-dependent follow-up explicit in the process model. A retained timer route sends an overdue supplier response to a human follow-up task.

Signal-based coordination

Use a business signal to connect a relevant change to the next activity. The retained design includes delivery confirmation before acceptance review.

Boundary errors and recovery

Describe error handling alongside the activity that can fail. The retained conversion example routes an error to document correction.

Request correlation

Give an event the business context needed to act on it. Define which request, task or process instance the event belongs to.

Visible exception work

Keep exception responses visible to responsible users. Separate authored event-route descriptions from live operational evidence.

01 / A closer look

Wait for the event that matters

A business stage may need a message, a person or a deadline before it can continue. Model these routes inside the state flow so that waiting has a business meaning and the next response remains visible.

  • Represent message waits and human tasks in the same stage
  • Use gateways to make the next route explicit
  • Read the state flow alongside the cases waiting there

02 / A closer look

Give exceptions an accountable route

Deadlines and errors should lead to an understandable next step. The retained procurement design connects waiting, overdue follow-up and document correction to explicit activities rather than hiding them outside the process.

  • Identify the business record associated with the event
  • Make escalation or correction work visible
  • Agree how failures and duplicate messages are handled by the integration

From design concepts to business work.

Discuss the objects, responsibilities and boundaries that make this capability useful in your environment.

MessageTimerSignalBoundary errorBoundary timerCorrelation contextConfigured response

Controls to design deliberately

The business record or case associated with each event

What happens when a message, deadline or error occurs

The delivery, duplicate-handling and recovery requirements

Explore sovereign AI requirements

Where this becomes useful.

Illustrative solution scenarios to shape a useful demonstration.

Continue a document handoff when a supplier acknowledgement arrives.

Create human follow-up after a configured response deadline.

Correct a failed document conversion before the process continues.

Connected capabilities.

See Inflow in the context of your organization.

Bring your business journey, AI environment and integration needs. Let’s explore the right starting point.

Request a demo