Skip to main content

Notifications

Power Pages - Design & Build
Suggested answer

Issue with cloud flow with power pages trigger

Like (0) ShareShare
ReportReport
Posted on 14 Mar 2024 15:22:38 by 123

Hi Guys,

We have deployed a  power page site and other components using solution. Here enhanced data model is being used. The site has few power automate cloud flow integrated and those flows have power pages trigger. After deploying to another environment as part of managed solution, the cloud flows are still pointing to the source environment (URL of the cloud flows are same as source environment) when we see from Edit power page site(from design studio)--->Cloud flows (integration) . Not sure how to change the URL or any step is missed.

 

Any support on this is highly appreciated.

Thank you.

  • Suggested answer
    SaiRT14 Profile Picture
    SaiRT14 1,618 on 14 Nov 2024 at 22:13:42
    Issue with cloud flow with power pages trigger
    pls try the following:
     
    • Go to Power Automate in the target environment.
    • Open each cloud flow, and ensure the connections for all actions and triggers are re-authenticated and updated for the target enviro
    • In Power Automate, edit each flow that has a Power Pages trigger.
    • Re-select the target environment’s Power Pages trigger in the flow trigger configuration.
    • Open the Power Pages site in the Design Studio in the target environment.
    • Go to Settings > Integration > Cloud Flows to review and update the flows.
    • You may need to remove and re-add the flows from this list to ensure they’re linked to the
    • If your flows are triggered based on hardcoded URLs or references in solution configurations, update these URLs to reference the target environment explicitly.
  • CU07111841-1 Profile Picture
    CU07111841-1 2 on 07 Nov 2024 at 18:48:36
    Issue with cloud flow with power pages trigger
    @UR-06110101-0  We ran into the same issue today and also couldn't figure out how to associate the Portal app user with the flow that came over to QA with our solution import.  Tried restarting the site, syncing...etc.  The JavaScript that calls the flow in test was always failing with an incorrect payload error eventhough the payload looked fine when viewed in the network tab.  The flow we're using was simple, so as a workaround, we recreated the flow in the test environment and added it to the site there.  We had to create a Site Setting that stores the guid of the flow, so we can dynamically get that for the JavaScript that calls the flow from the portal code.  This is working and the new flow created in the Test environment stays even when we import a new solution from dev.  Not ideal that we have to update the flow in multiple environments if it needs to change, but it is working for now.
  • johnsonjames Profile Picture
    johnsonjames 4 on 06 Nov 2024 at 20:36:17
    Issue with cloud flow with power pages trigger
    Have you tried environment variables? Before I export a solution with environment variable, I change URL to target environment's URL. 
  • UR-06110101-0 Profile Picture
    UR-06110101-0 2 on 06 Nov 2024 at 01:06:39
    Issue with cloud flow with power pages trigger
    Does anyone have a solution for this? I am having a cloud flow that is using the power pages trigger. The cloud flow is working fine on dev but after making the deployment to QA is failing with an error. The issue is that the cloud flow in the QA environment do not have the portal application user associated but not able to manually add it. 
  • JS-21080819-0 Profile Picture
    JS-21080819-0 2 on 21 Aug 2024 at 06:54:31
    Issue with cloud flow with power pages trigger
    We have just run into this issue as well. 
     
    The solution we found was to reference the Relative URL of the provided endpoint within our Power Pages site - rather than the full endpoint provided. Similar to what you have described, this stayed static after deployment from DEV to our UAT environment.
     
    URL Shown in UAT Settings:
    https://my-site.powerappsportals.com/_api/cloudflow/v1.0/trigger/<trigger-guid>
     
    URL Referenced when triggering:
    /_api/cloudflow/v1.0/trigger/<trigger-guid>
     
    Hopefully this works for others!
  • oliver.rodrigues Profile Picture
    oliver.rodrigues 8,988 on 26 May 2024 at 12:42:33
    Re: Issue with cloud flow with power pages trigger

    last I heard is that this issue is fixed, can you check your portal version? 

  • EricCahoon Profile Picture
    EricCahoon 14 on 06 May 2024 at 15:43:55
    Re: Issue with cloud flow with power pages trigger

    @OliverRodrigues Have you heard anything back from MS?  Our team is facing this issue and the manual work around is a concern for our DevOps team.

  • oliver.rodrigues Profile Picture
    oliver.rodrigues 8,988 on 20 Mar 2024 at 17:37:44
    Re: Issue with cloud flow with power pages trigger

    Yesterday I have escalated this issue with Microsoft but haven't heard anything yet.

     

    I noticed one thing in the release notes that could be the fix: Power Pages Release Version 9.6.2.x - Release Notes | Microsoft Learn

    "Flow ID is used to identify Power Automate flow to enable healthy ALM."

     

    This may actually be the fix available in Portal 9.6.2.x, however mine hasn't been updated to that version yet so I can't tell for sure. I also didn't receive confirmation from MS if that's what they mean from that fix.

  • Atmaram90 Profile Picture
    Atmaram90 123 on 20 Mar 2024 at 09:31:08
    Re: Issue with cloud flow with power pages trigger

    Thank you @OliverRodrigues for the workaround. It works fine but the problem is next time when we import another solution from the source environment, the flows (copied earlier) doesn't get updated and we have to again create copies and reconfigure. Any comment on this?

  • oliver.rodrigues Profile Picture
    oliver.rodrigues 8,988 on 15 Mar 2024 at 11:45:14
    Re: Issue with cloud flow with power pages trigger

    I am facing the same issue and have a support ticket open with Microsoft but without a proper solution yet.

     

    As a workaround what I had to do was create a copy of the flow in my target environment/re-add to my Site and update the JS URL

    As a good practice, I created a site setting with the GUID of the flow and pointed my JS to that GUID (it's an improved work around)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November 2024 Newsletter…

November 2024 Community Newsletter…

Community Update Oct 28…

Power Platform Community Update…

Tuesday Tip #9 Get Recognized…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 144,524

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 64,373

Leaderboard

Featured topics

Loading started