Overview
A transaction instance is a single, real-time execution of a Push Model business transaction. It represents one complete run of the workflow — for example, the end-to-end journey of a specific order, identified by its order ID, from the first stage event to the last.
BAM creates a transaction instance automatically when it receives the first event for a new correlation key via the BAM API. As your integration emits events at each subsequent stage, BAM updates the instance with the new stage data, building a live record of that execution's progress.
Business value
Transaction instances give your operations team a concrete, searchable record of every tracked workflow execution. When an alert fires or a customer raises a support request, you can navigate directly to the affected instance, see exactly which stages completed and which did not, inspect the tracked property values at each stage, and act on what you find — all from a single view in Turbo360, without escalating to a developer.
How it works
When BAM receives the first stage event for a new correlation key, it creates a transaction instance in the Inprogress state. Each subsequent event advances the instance through the configured stages. BAM evaluates instance state continuously and updates status as conditions are met.
Each transaction instance has the following attributes:
- Correlation key — The value of the tracking property that uniquely identifies this execution (e.g. a specific
OrderId). BAM uses this key to link all stage events from the same run into one instance. - Status — The current evaluation state. Possible values: Inprogress, Success, Failure, Cancelled.
- Stage completion — A record of which stages have been reached, when each completed, and what property values were captured.
- Tracked properties — The key-value pairs extracted from stage events and stored against the instance for search and filtering.
- Duration — The elapsed time from the first stage event to the last received event, or to the current time if the instance is still in progress.
Instance status values
- Inprogress — BAM has received at least one stage event but not yet all configured stages.
- Success — All configured stages have been reached, or a stage configured with Mark complete was triggered.
- Failure — A stage configured with Mark failed was triggered, or a user or automated process explicitly marked the instance as failed.
- Cancelled — The instance has been marked as cancelled.
Reprocessing
Push Model instances can be reprocessed when the source event is still available. Reprocessing replays the event through the configured transaction flow and creates an updated instance record. The original instance is retained. This is unique to the Push Model — Pull Model instances cannot be reprocessed.
Searching and filtering instances
You can search and filter transaction instances in the Tracking section of BAM. Available filters include tracked property values, instance status, date range, and stage completion state. For Custom Logging type transactions, a DSL query language is also available for advanced filtering across property values.
Limitations
- Instance data cannot be manually edited. If a stage event was emitted with incorrect property values, the stored instance reflects those values. Reprocessing is the only way to update an instance with corrected data.
- Instances persist according to the purging policy configured on the business process. Once purged, instance data cannot be recovered.
- Full-text search across instance property values requires an index to be created for the relevant property. Unindexed properties support exact-match filtering only.