Thanks for the update! 😊 As noted, Azure Logic Apps support only one trigger per workflow in the designer. To handle multiple trigger types (such as HTTP requests and scheduled runs), the best approach is to:
Create separate Logic App workflows—one for the HTTP trigger and one for the scheduler.
Use a controller Logic App that is itself triggered (via HTTP or schedule).
From the controller, invoke the main processing logic—either by calling a child workflow or passing control accordingly.
You followed this pattern perfectly by implementing a controller workflow that invokes the necessary logic based on the type of trigger. It’s an ideal workaround that keeps each workflow focused and maintainable.
Great work on resolving the issue! If this approach helped, please do not forget to click "Accept the answer” and Yes
wherever the information provided helps you, this can be beneficial to other community members.
If you have any other questions or still running into more issues, let me know in the "comments" and I would be happy to help you.