Thanks, @Mike Hardy ! This appears to be a known issue with certain versions and the workaround is to revert back to 16.5.5
--if possible, could you try that out and see if that helps?
If that doesn't work, please send us the following info at azcommunity at microsoft dotcom
(subject line of your email to read "attn:murnun") so that we can investigate further:
- Resource ID for Logic Apps (can be located in Azure Portal -> your Logic Apps -> Properties):
- Activity logs from VS:
Getting Logs:- Open developer command prompt for VS 2019
- Run the following command to start VS with activity logging enabled. "devenv.exe /log".
- Repro the issue in this instance and close it.
- You can find the activity log at the location :
a. Go to %APPDATA%\Microsoft\VisualStudio\
b. Open folder specific to visual studio version eg: 16.0_e63236cd
c. You will find the log file - ActivityLog.xml here.