Skip to main content
An entity profile connects runs by customer_id, agent_id, or another business reference. Review their history and metrics without merging threads or contracts.

Define the entity

Create a profile type in Entity Profiles and choose the reference key that identifies your entity. For example, an Agent profile type can use agent_id. Have your services attach that ref to relevant threads:
For OTLP ingestion, set threadify.ref.agent_id on the span. Ordinary business refs associate history; they do not give every matching thread the same identity. See references and correlation. With the CLI, a basic profile-type file looks like:
Use the returned type ID. The CLI can create a named profile before activity arrives. Registry controls how many profiles the installation may have.

Choose the metrics

Configure metrics on the profile type in the dashboard, such as failed refunds, approval violations, or execution duration. Metrics must be configured explicitly. Open a profile to review metrics, delivery health, and history. Select a thread for its steps and validation evidence. New activity may lag while it is archived.

Completion is not compliance

A retried workflow can complete successfully despite earlier failures or rule violations. Compare these measures:
  • Completion rate: how often the workflow eventually completed.
  • Failed steps and retries: problems encountered along the way.
  • Validation findings: whether the recorded behavior obeyed its contract.
  • Delivery health and trend: an aggregate signal to investigate, not proof that every rule passed.

Walkthrough

The walkthrough shows metric configuration, profile metrics, delivery health, and navigation into execution evidence: