Help center for technical users
Browse terms and frequently asked questions below, or use the global search (Ctrl+K) to find something specific.
- Chain IDalso: clientTrackingId, client tracking ID
The Invictus name for the Azure Logic Apps
clientTrackingId. It groups all flow traces belonging to the same transaction.Because async flows may regenerate this ID during routing, developers must reset it as early as possible in each workflow to keep the chain intact.
- Claim-check patternalso: claim check
An Invictus Framework behavior used in . When a published message has a body that exceeds a size limit (default 20,000 bytes), the Publish action offloads the body in Azure Blob Storage instead and adds a reference in the message.
The Subscribe action gets the body from storage by the reference.
See also the claim-check integration pattern.
- DSAV
Stands for Domain, Service, Action, and Version — four special that Invictus reads during to map workflow runs to the correct Dashboard flow.
These values must match the corresponding properties configured on the flow in the Dashboard. Invictus also reads a
WorkflowNamefield alongside DSAV to resolve the exact flow mapping.- Exception Handler
An Invictus Framework component that resolves the actual error from a failed Azure Logic App workflow run. It exposes a
/api/ResolveExceptionendpoint that retrieves the underlying error message — replacing the generic Azure error — and can optionally translate it to human-readable text via a configurable regex translation table.- Execution tree
The hierarchical view of parent and child runs linked within a single . Invictus builds this tree from the
x-iv-parent-workflow-run-idtracked property set by developers when chaining workflows.The execution tree is visible in the Dashboard flow detail view and shows the full processing chain for a message.
- Flow
A named message chain — a logical grouping of related flow traces sharing a common origin. Flows are organized in folders and defined by a name, optional mappings, and business properties.
- Flow trace
A single tracked message instance within a . It records the full lifecycle of one execution: status, timestamps, properties, and the chain of processing steps.
Each flow trace can be searched and inspected in the Dashboard, and is loaded via .
- Flow trace importingalso: import job
The process of ingesting data into the Dashboard — automatically via Logic Apps or Function Apps, or manually. Once imported, messages become visible and searchable in the Dashboard
- PubSub
An Invictus Framework component that enables publish/subscribe messaging between Azure Logic App workflows. It uses Azure Service Bus as a message broker. For messages exceeding a size limit, PubSub offloads the body to Azure Blob Storage. See also .
- Sequence Controller
An Invictus Framework component that runs Azure Logic App workflows in a fixed order. It does not use concurrency throttling to enforce this.
Each workflow claims a spot in a named sequence. It waits its turn, does its work, then signals the next one to start.
This keeps workflows in order even when they start at the same time. It does not block the whole Logic App.
- Tracked properties
Custom metadata fields set on Azure Logic App actions that Invictus reads when importing flow traces. They drive the key Dashboard features:
- and
WorkflowName— map workflow runs to the correct flow. x-iv-parent-workflow-run-id— links child workflows to their parent to build the .Milestone/EventText— annotate processing steps shown in the flow detail view.x-iv-messagecontent-*— expose input/output content of specific actions in the Dashboard.
- and
- Transco
An Invictus Framework component (originating from a BizTalk pattern) that enriches messages during processing. It can:
- Promote values from an SQL database into the message or context, using the message content or context to build the query.
- Transform XML content using an XSLT stylesheet stored in Azure Blob Storage.
Troubleshooting
Got questions? You may find the answer here. If not, feel free to create a support ticket.