Guide for handling 'your flow has a new trigger'?

Allan Delmare

I've seen several topics and discussions come up, but I've yet to find a guide for 'what to do' … is there a TL;DR that anyone can point me to?

context: I've inherited a power automate setup, I'm not super familiar with the ins and outs of it, so I'm looking for a shortcut to what needs to be updated/changed in order to keep things working and not come crashing down in the short term. Thanks!

Kelly Hogan

I don't have an answer, but I am interested to see what others say! I keep getting that notification too, but I am too deep in other projects to really stop and try to figure it out at the moment!

Austen Brown

Misunderstood the question. Refer to Alex's response below.

Alex Wong

@Austen Brown I help a client of mine handle this and does not need to do the steps you mentioned. The flow have a new trigger URL, assuming this is what the OP is asking about:

Then the flow does not need to be updated at all. What needs to happen is change the "calling" app.

For example:

You created an adaptive card custom tile that is added to RE NXT (i.e. gift page, constituent page, or home page). RE NXT when the page is called, will trigger the URL that is calling the flow to run and return adaptive card to display. The flow that creates the adaptive card has 2 URL right now, the existing (OLD) one, and a new (assigned by MS recently due to their change) one, BOTH will trigger the flow to run and return an adaptive card to RE NXT. After 11/30, the old one will no longer work.

What needs to be done is:

1. Edit your flow (no need to do anything in the flow and save) and go to the trigger action at the top, the NEW URL is right in the trigger for you to copy
2. go to any URL Encoder tool on web and put the URL there and encode it
3. go to developer.blackbaud.com and your application where the custom tile is defined.
4. update the add-in for the custom tile where it is calling the flow's OLD encoded URL and replace it with NEW.
5. DONE

Jason Guan

https://community.blackbaud.com/discussion/comment/308725#Comment_308725

Would you know how to subscribe to the Sky API Webhooks using the "New URL"?

Alex Wong

SKY API webhook had an issue that some said it is fixed from Microsoft, I have not attempted to do this yet, but will have to this week/next week as I have a ton of webhook registered too.

@Ben Wong @Erik Leaver any info you can provide. Also, I try using the Get Subscription List API endpoint and did not retrieve ANY webhook I registered. Is there a bug there? I have almost every event type registered to a flow and they are currently still getting triggered.

Austen Brown

https://community.blackbaud.com/discussion/comment/308725#Comment_308725

Misunderstood the question. Thanks for clarifying. I'll edit to point them to your response.

Kelly Hogan

Thanks for the assistance @Alex Wong and @Austen Brown!

Ben Wong

https://community.blackbaud.com/discussion/comment/308734#Comment_308734

Hey @Alex Wong and @Jason Guan, we don't have a way to update the URL on an existing webhook subscription, so the only way to use the new URL from Microsoft is to create a new webhook subscription for each event type.

However, I just tried doing this and ran into an issue when performing the CloudEvents handshake using the OPTIONS method. In the instructions I shared back in 2021 the Request Trigger could be used to set the method to OPTIONS. However, OPTIONS doesn't appear in the method list (I can't remember if it used to before but I assume it did since I didn't mention it) and while it gets accepted as a custom value, it doesn't seem to work. Testing the Request Trigger with other methods work, but I get a 404 when using OPTIONS. It appears to be a bug but will contact Microsoft to confirm.

Also, the GET Subscription List works for me. Make sure you're using it in the correct environment where your webhooks are subscribed.

Alex Wong

Today's PA User Group, we went over various situation of new http trigger URL.

@Erik Leaver if you can post the video (when ready) here, will help others in the same boat

Alex Wong

Looks like MS did not turn off the old URL…

even though I replaced all old with new before 12/1. I can't do the same with the webhook, but looking at my run history, looks like old URL still working… anyone got any info from MS?

Jason Guan

https://community.blackbaud.com/discussion/comment/309093#Comment_309093

https://community.blackbaud.com/discussion/comment/308955#Comment_308955

It seems that Microsoft is aware of the issue with making the OPTIONS call and are working to fix this issue. Until then, the old URLS will continue to work until the issue has been fixed.