Analytics and execution data

DecisionHub provides several views of runtime activity. They serve different audiences and retain different data:

Area	Primary purpose
Execution History	Investigate individual runs and debug data
Statistics	Review API usage across solutions
Reporting	Build datasets, reports, and dashboards from execution records
Analytics workspace	Explore organization analytics in Redash
Integration Activity	Investigate trigger and publisher deliveries

Enable decision analytics

For supported HubItems, execution input/output is persisted for analytics only when both levels are enabled:

1. Organization analytics is enabled in Organization Settings.
2. Analytics is enabled in the Decision Table or Workflow Settings.

HubItems default to analytics off. Turning on only one switch does not create analytics execution records.

Example

Organization analytics	Workflow analytics	Analytics records stored?
Off	Off	No
Off	On	No
On	Off	No
On	On	Yes

This two-level control allows an organization to make analytics available while individual asset owners decide whether a process is appropriate for payload persistence.

Decide what is safe to store

Execution payloads can contain names, identifiers, financial values, or other sensitive information. Before enabling analytics:

• minimize input/output models to required business fields;
• confirm the purpose and audience;
• review organization and HubItem access;
• establish retention policy;
• avoid secrets in payloads and error messages;
• understand regional or contractual data obligations.

Persisted records keep the input/output distinction, correlation ID, and attribution to the models used by the execution. That supports field discovery and tracing without treating every JSON property as an ungoverned metric.

Use correlation IDs

A correlation ID links several operational views. For an unexpected business outcome:

1. Find the API call or integration delivery.
2. Copy its correlation ID.
3. Search Execution History.
4. Inspect the deployed HubItem/version, input, output, and permitted debug data.
5. Compare with reporting or analytics records for the same business event.

Correlation is more reliable than searching only by timestamp when traffic is high.

Redash analytics workspace

Select Analytics from the main navigation to provision or open the organization's Redash workspace when available. Select the correct organization and solution first. If no tab appears, allow the browser pop-up and try again.

In Redash, use organization-approved data sources and dashboards. Treat exported results according to the same access and retention rules as DecisionHub data.

Execution History

Filter records by correlation ID, HubItem type, executor, and date range. Open a record to inspect its business input/output and debug details where captured and permitted.

Example investigation:

Customer reports application APP-1042 was declined
  → locate application/API correlation ID
  → open Workflow execution
  → find RiskScore node returned 65
  → inspect Scorecard partial contributions
  → verify deployed Scorecard version and input mapping

Deleting an execution record is governed by permission. Retention Policies provide consistent automated expiry and can optionally remove debug data.

Statistics

Organization Statistics summarizes API calls and supports solution search. Use it to identify volume trends and unusual usage, then open the relevant API key or execution records for diagnosis. Statistics are not a replacement for consumer-side monitoring and alerts.

Common problems

Symptom	Check
No analytics records	Both organization and HubItem switches, supported HubItem type, and new executions after enablement
Analytics link does not open	Organization selection, feature availability, and browser pop-up permission
Debug tab absent	Execution was not run with Debug, data expired, or user lacks permission
Report fields unavailable	Reportable non-debug executions exist and models attribute those fields
Record disappeared	Retention policy or permitted manual deletion