Issue summary – Logic Apps Standard parameter confusion

Question

In a Logic Apps Standard (stateful) workflow, I can run successfully in draft after setting definition.parameters defaultValues to @appsetting('...'). However, when I publish the workflow, those changes don’t appear in the published version — it behaves like it’s still using the previous workflow definition/parameter values. It looks like publish isn’t syncing the updated definition, or something is overwriting it post-publish. Any ideas what typically causes this (e.g., parameters.json overriding, deployment slot/app setting mismatch, save vs publish vs refresh quirks)?

Answer 1

When you encounter issues with parameters not syncing correctly in a published Logic Apps Standard workflow, there are several factors to consider:

1. Parameters File: Ensure that your parameters.json file is correctly configured and that it is not overriding the values set in the definition.parameters during the publish process. If the parameters file contains different values, it could lead to the behavior you're experiencing.
2. Deployment Slots: If you are using deployment slots, verify that the correct slot is being published and that the app settings in that slot match your expectations. Sometimes, settings in different slots can lead to confusion.
3. App Settings: Check if there are any app settings that might be overriding your parameter values after the workflow is published. If the app settings are set to different values than those defined in your workflow, it can cause discrepancies.
4. Save vs. Publish: Be aware of the differences between saving and publishing your workflow. Changes made in the draft mode need to be published explicitly; otherwise, they may not reflect in the live version of the workflow.
5. Refresh Quirks: Sometimes, the Azure portal may not immediately reflect the latest changes due to caching. Try refreshing the portal or checking the workflow definition through other means (like Azure CLI or PowerShell) to ensure that the changes have been applied correctly.

By reviewing these areas, you should be able to identify the cause of the parameter confusion in your Logic Apps Standard workflow.