Missing or Incomplete Log Data v2

A missing value can be caused by search scope, execution state, redaction, deferred enumeration, size handling, storage failure, or a different activation context.

Confirm the instance and scope

Check Site, Environment, Workflow key, instance key, activation mode, time range, Node, and result filter. Browser time is local; compare exact timestamps when another system uses UTC.

Use non-indexed chronological search when you need Load entries before. Indexed content search can return a different evidence window.

Check execution state

Live logs are incomplete while a Step or deferred output is still running. Refresh after completion. Cancellation or host failure can leave a final Property unavailable even when earlier rows were stored.

For Streams and lazy Arrays, values and counters are captured as the downstream consumer enumerates them. An unconsumed or partially consumed sequence cannot have a complete item log.

Logs from local Cluster invoked Workflows may also be delayed in arriving.

Check value handling

Logging.Redact removes selected Property values from logging.
Connection masks protect credential values independently of Workflow redaction.
Large or binary values can be stored as downloads, represented by metadata, or truncated.
Some failed storage operations retain the activity row without every Property payload.
Designer Debug can expose captured response values that are not ordinary Workflow Returns.

Do not weaken production redaction merely to fill a log. Reproduce with safe synthetic data, a non-sensitive Sample, or a purpose-built diagnostic return.

Open the parent or child instance when the activity occurred in a Sub-Workflow. Retry the download while authenticated and within the retention period. If repeated small non-redacted values are absent across unrelated instances, preserve the instance keys and contact support with the narrow evidence set.

Use Indexed search to find logs for a known value quickly

This feature allows you to search on a known identifier like an invoice number or transaction ID that has appeared in the logs. It is limited to data that is included in the recorded logs (i.e. within the truncatation cutoff) and only the first 10 matches will display.

Use MCP or AI Assistant for log deep dives

These tools are able to execute a large number of targeted log searches very quickly. This approach is recommended when there is a large volume of data to consider, exact timing of incident is unknown or a pattern of behaviour is being validated rather than investing a single instance of an issue.