Skip to main content

Help center for technical users

Browse terms and frequently asked questions below, or use the global search (Ctrl+K) to find something specific.

Skip to glossary list
C
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 implemented in : when a published message body exceeds the configured size limit (default 20,000 bytes), the content is automatically stored in Azure Blob Storage and the message is sent with an empty body.

The Subscribe action transparently retrieves the content from storage, so consumers receive the full payload without needing to handle the offload themselves.

See also the claim-check integration pattern.

D
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 WorkflowName field alongside DSAV to resolve the exact flow mapping.

E
Exception Handler

An Invictus Framework component that resolves the actual error from a failed Azure Logic App workflow run. It exposes a /api/ResolveException endpoint 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-id tracked 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.

F
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

P
PubSub

An Invictus Framework component that enables publish/subscribe messaging between Azure Logic App workflows using Azure Service Bus as a message broker. Workflows interact with it via three HTTP endpoints: Publish, Subscribe, and Acknowledge.

For messages exceeding the configured size limit, PubSub automatically applies the — offloading the content to Azure Blob Storage and restoring it on Subscribe.

S
Sequence Controller

An Invictus Framework component that ensures Azure Logic App workflows execute in a defined order without relying on concurrency throttling. Workflows take a numbered position in a named sequence, wait their turn, perform their work, then signal completion so the next workflow can proceed.

This allows parallel-triggered workflows to process messages in order without blocking the entire Logic App.

T
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.
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.

Frequently asked questions​

Got questions? You may find the answer here. If not, feel free to create a support ticket.

Frequently asked questions. If you cannot find an answer, you can create a support ticket on GitHub.