Logic Apps Standard: Draft runs successfully but published (scheduled) version reverts / fails after publish

I’m working with a Logic Apps Standard (stateful) workflow.

In the draft/designer version, the flow runs successfully. I have workflow parameters defined in definition.parameters with defaultValue referencing app settings, for example:

"defaultValue": "@appsetting('AcumaticaClientId')"

When I manually run the draft version, authentication and downstream actions work as expected.

However, after I Save / Publish the workflow, the scheduled (published) version behaves differently:

• It appears to revert to an older version of the workflow

The updated parameter defaults referencing app settings do not seem to be applied

The published run fails, even though the draft run succeeds with the same logic

This makes it feel like the publish step is not propagating the latest workflow definition, or that something (e.g. parameters.json, deployment artifacts, or runtime parameter binding) is overriding the published version.

I’m trying to understand:

Why the draft version can resolve app setting–based parameter defaults correctly

Why those same changes don’t carry across after publish

What the correct pattern is to ensure parameter values are consistent between draft and published/scheduled runs in Logic Apps Standard

Has anyone seen this draft vs published mismatch before, and what’s the recommended fix or deployment approach?