I am using the new tier of logic apps that enable multiple workflow per logic app. I have observed two problems.
My timer based trigger is scheduled to run on 10:30 but is executed at 10:15 (consistently). Other triggers that are also expected to run on the 30th minute of an hour also execute on the 15th minute of the hour. Is there any reason?
I have currently deployed 6 workflows in my logic app. However, for 3 of the 6 the portal do not show the previous runs (meaning, I do not see the whole section that should be there, not even an empty table) nor do they actually trigger. (Two of them are now disabled but the third is a timer based trigger that should run but does not.) What I have found in application insights is that whenever I go in the portal and click on these workflows, the underlying storage operation returns a 404 error. This means to me that the workflow is not found. What is odd then is that the workflow itself shows in the portal. But when I click on the workflow, I only see the general information but no previous runs and no workflow URL.
I am deploying in the D1 tier using Bicep templates and the workflows itself are deployed using Azure DevOps as a ZIP.
This seems to me like an underlying platform issue.
PS: I also asked this question on Stack Overflow since I was unable to post anything here before (https://stackoverflow.com/questions/69721168/azure-logic-app-workflows-not-found-and-timer-executed-15-minutes-prior-to-expe).