Workflow Log Redaction v2

The Runtime can replace selected Property values with (Not Logged) in Workflow Logs while leaving the live runtime data unchanged.

Use redaction for credentials, tokens, personal information, or other values that should not be retained in Workflow Logs.

Configure redaction

Add Logging.Redact: true to the Property in Workflow YAML:

Password:
  Type: string
  Logging:
    Redact: true

The current canvas does not expose a redaction control. Edit the Property in Code view or use an authorized Builder tool, then resolve validation problems before saving.

Redaction is compiled into the published Workflow. Save the change to publish it to Test, then promote or publish that revision to every Environment where it must apply. An older published revision keeps its older logging rules.

Redact an Object or Array field

Redaction can apply to a complete Property or a named field at any depth:

Customer:
  Type: object
  Properties:
    displayName:
      Type: string
    credentials:
      Type: object
      Properties:
        username:
          Type: string
        password:
          Type: string
          Logging:
            Redact: true

For an Array, the nested rule applies to that field in every item:

Customers:
  Type: array
  Properties:
    id:
      Type: string
    accessToken:
      Type: string
      Logging:
        Redact: true

Putting Logging.Redact: true on the parent hides its complete logged value. A parent exclusion also makes descendant rules unnecessary.

What redaction does not do

Workflow Log redaction:

• Does not change the value received by the Node or a downstream Step.
• Does not automatically carry into every later Property that receives the value. Apply the appropriate rule at each logging boundary.
• Does not sanitize designer Debug results, Node-generated logs, exception messages, diagnostics, external destinations, or values returned to callers.
• Does not turn an ordinary Workflow Property into encrypted storage.

Review the complete data path and avoid copying sensitive data into unredacted text or errors.

Connection masking

Connection masking is separate. A Node's Connection definition marks sensitive Connection fields, and Flowgear protects the complete Environment value in its credential store. Console receives ********** for masked fields when you edit the Connection.

Selecting that Connection through a connectionKey does not mean that every value the Node later returns is redacted. Apply Workflow Log redaction to any sensitive Workflow data the Node exposes.

See also

See Masked Data Type, Workflow Properties, and Workflow Logs Screen.