Pinned Data Section — Node Inspector Tab

What Is Pinned Data?

Pinned data is an optional secondary payload returned by an executor alongside the normal output. Unlike output data (which lives only in ExecutionMemory for the duration of the execution), pinned data is written to a persistent store and associated with the ProcessElement (the node instance in the workflow definition).

Pinned data is useful for:

Storing the last API response for reference without re-executing
Accumulating results across multiple executions (e.g., a counter)
Preserving expensive computation results for reuse

How an Executor Returns Pinned Data

// Returning both regular output and pinned data
return NodeExecutionResult.Success(
  output: new {
    processedCount = 42,
    successRate = 0.98
  },
  pinnedData: new {
    lastRunAt = DateTime.UtcNow,
    cumulativeProcessed = previousPinnedData?.cumulativeProcessed + 42 ?? 42,
    lastSuccessRate = 0.98
  }
);

In the Node Inspector

When pinned data is present, the inspector shows a third JSON tree section labelled Pinned Data with a pin icon (). The section only appears if nodeInspectorData.pinnedData !== null.

Pinned Data Persists Across Sessions Even after you close the browser and return later, the Pinned Data section will still show the pinned data from the most recent execution that produced it — because it is loaded from the server, not from the SignalR buffer.

← Output Data Section Next: Timing and Retry Info →