Know Which Automation Warnings Actually Need Fixing

Dynamic value chips now have three states instead of two. A yellow chip means the value is real but nothing in this workflow supplies it, so it will render blank. Red is now reserved for values that do not exist at all, which usually means a typo worth fixing.

What does each colour mean?

The colour tells you whether the value will fill in, render blank, or never render at all. Every chip lands in one of the three.

• Blue means the value is available in this workflow. It can be filled from the contact record, a system value such as the current date, or an earlier step.
• Yellow means the value is real, but nothing in this workflow supplies it. An example is {{sheet.10.rowNumber}} in a workflow with no Google Sheets step. It renders blank unless another workflow passes it in through Add to Workflow with pass input trigger parameters.
• Red means the value does not exist. Nothing matches it, for example {{applesheet.10.rowNumber}}, so no workflow will ever render it.

Does a yellow chip stop my workflow publishing?

No. Yellow is a warning, not a block, so you can save and publish as usual. It is there to prompt you to check whether something else supplies that value before you rely on it.

Why was this changed?

Every value that would not render used to show red and say it was not recognised, which made a deliberate setup look like a mistake. Dropping {{invoice.url}} into an Add Notes action in a workflow that no invoice trigger starts, or handing a value from one workflow to another, both turned red. Splitting the states puts red back on the cases worth acting on: red means the value is wrong, yellow means check whether something else supplies it.

Do the spaces inside the brackets matter?

Not any more. Attribution Url is stored as {{ attribution.first.url }} with spaces, and typing {{attribution.first.url}} without them used to come back red. Both forms match now. This changes what you see only, because values resolve when the workflow runs exactly as they did before, so anything that worked before still works.

You will find this in the workflow builder, on any field where you insert a dynamic value.