Troubleshooting

When a flow is not doing what you expect, start with the simplest possible question:

Did the runtime load, did the trigger fire, and did the node receive the data you think it received?

That order solves most issues quickly.

Runtime not loading

Check:

• the script snippet belongs to the application you think it does
• the current domain is allowed by the application
• the app has been published to the environment you are testing
• the browser can actually download the runtime script
• there are no CSP or network errors blocking the load

Event not triggering

Check:

• the trigger type matches the real browser behavior
• the event name matches exactly, including fx. prefixes where relevant
• the application setting for that built-in listener is enabled
• event queueing is not holding the event before Release Queue runs
• the selector, threshold, or route condition matches the page you are testing

If you are unsure, start a debug session and verify that the expected event data is actually reaching the flow.

Flow not publishing

Check:

• all required node properties are filled in
• the flow belongs to the application you expect
• any custom-node or official-node inputs are configured correctly
• validation messages are resolved before publishing

Consent-gated node not executing

Check:

• the consent snapshot contains the values you expect
• your conditions are reading the correct consent path
• the Event Trigger for your CMP update event matches the event your consent library emits
• the CMP update Event Trigger has Bypass queue enabled when application queueing is enabled
• queued applications call Release Queue after consent categories are updated
• the node is downstream of the right consent logic

Custom node problems

Check:

• the input node defines the fields the calling flow expects
• the caller passes the required values
• the internal flow handles empty or malformed inputs clearly
• any required vendor script is loaded before function calls depend on it

Official integration problems

Check:

• the official vendor node is being used in the correct action mode, such as load versus track
• any required install or initialization step happens before event calls
• your parameter names match what the vendor expects
• you republished after changing the flow if you are testing production behavior