Hi Louis,

Thanks for your reply and explanation.

Note that we do assign the parameter a value when executing the script inside a workflow job. In the sample notebook I also defined the parameter using the widget and assigned it a value directly.

I'm trying to then understand why the following code works in v2025.15:

declare or replace var query = "SELECT '${PARAMETER_1}'";
EXECUTE IMMEDIATE query;

Isn't ${PARAMETER_1} also unbound and should throw the same error?

And using :PARAMETER_1 is working fine in v2025.10. Was that an unintended behaviour and we should stay away from using it this way?

Thanks