Logic App Standard does not generate a Trigger-URL in development slot

hello638294 0 Reputation points
2024-10-01T12:08:22.2+00:00

Hi,

I am facing the issue that my workflows with http triggers ('When an HTTP request is received') in the development slot of my standard logic app don't have trigger url's generated after saving. In order to test the changes made in the development slot, I need a trigger URL to call the workflow from my other app. This way I can see if the changes I made work or not. In the production slot every 'When an HTTP request is received'-Trigger has a Trigger-URL which I can obviously I can call.

This is the workflow in the production slot:

User's image

And here is the workflow from the development slot:

User's image

When I click 'save' it saves the workflow successfully but does not generate the Trigger-URL for the HTTP-Trigger in the development slot.

Does anyone know how exactly the dev slots work and how to get the Trigger-URL's for the development slot in order to work with the workflows?

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,228 questions
{count} vote

2 answers

Sort by: Most helpful
  1. JananiRamesh-MSFT 28,321 Reputation points
    2024-10-02T17:12:31.4833333+00:00

    @hello638294 Thanks for reaching out. Unfortunately, I am unable to reproduce this issue on my end. It seems the HTTP URL was not generated upon saving, which could be due to a browser issue. Please try using a different browser. You can also retrieve the same workflow URL from the Overview page as shown below.User's image

    do let me know incase of further queries, I would be happy to assist you.

    0 comments No comments

  2. WyrzykowskiAdam-8446 0 Reputation points
    2024-11-21T10:26:24.91+00:00

    Same for me, I'm using current version of Edge browser

    User's image

    User's image

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.