Skip to content

Common HighLevel Workflow Problems

Inspect the failed run and check whether the mapped value existed when the action executed. Compare the configured field with the installed action’s input definition.

Inspect the exposed outputs from a successful controlled run. Verify the output type and field name rather than guessing from a Microsoft Graph response.

Determine why the trigger repeated and whether the first run already changed a resource. Duplicate handling and idempotency are action-specific and require implementation review.

Record the visible action name, sanitized values, execution order, expected outcome, and timestamp. Keep secrets, customer files, and private URLs out of diagnostics.

Related: outputs, verify setup, and support.