Share
ReportHello: please help. I am stuck with a ghost HTTP request trigger!
I created a new flow with an HTTP Request trigger. I renamed the trigger to "manual" and saved the flow which gave me a URL. So far so good. During my test, the request wasn't receiving so I thought I should get a new URL. I deleted the trigger and recreated a new one but as soon as I hit save, the new trigger was renamed to "manual" and the identical URL was generated. I created a brand new flow from scratch, added the HTTP request trigger and once again, renamed to "manual" with identical URL. Then I inspected my past flows and WHEREVER I had HTTP trigger, they were all renamed to "manual" and URL changed to the one from my initial flow.
Things I have tried:
1. Changed the JSON schema, conditions and permission to force PA to create a new trigger.
2. Reboot, new browser, incognito mode.
3. Duplicate a flow.
Did I corrupt the backend with naming the trigger "manual'" ??
I have the same question (0)
All responses (
Answers (
809
