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.

Answer 2

Hi @Kurt Carvalho ,

Check below potential causes and things:

1. Double-check if there are any parameters defined in parameters.json that might be overriding your values after publishing. This can happen if you have a different set of parameters governing production.
2. Ensure that your application settings (@appsetting(...)) in your published Logic App correctly align with what's set in draft mode. Any mismatch could lead to your workflow not recognizing the updated values.
3. Make sure there are no environment variables that might be affecting the behavior. Sometimes deploying Logic Apps in different environments might result in using unintended values.
4. If you're using deployment slots, remember that each slot can have its own app settings. Make sure the settings in the live environment reflect those you want to use.
5. Sometimes, changes in the Logic Apps designer might not take full effect until they are explicitly published. Ensure you’re hitting publish after saving your changes.

Keep in mind that sometimes the Logic Apps designer can have quirks. Try refreshing the portal or rechecking the parameters after publishing to see if they update.

References:

• Create cross-environment parameters for workflow inputs in Azure Logic Apps
• Troubleshoot and diagnose workflow failures in Azure Logic Apps
• Deploying Logic App Standard resources through DevOps pipelines

Hope it helps!

---

Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you.