microsoft-teams-apps-requestateam icon indicating copy to clipboard operation
microsoft-teams-apps-requestateam copied to clipboard

Check Availability Fails

Open AlanMRichards opened this issue 4 years ago • 7 comments

The check availability button has an error and is not running. I have checked the App monitor in PowerApps and get a Bad Gateway error and this in the app.

image

AlanMRichards avatar Oct 01 '20 13:10 AlanMRichards

@AlanMRichards the most common reason for this error is that the data connections and variables inside the 'CheckTeamAvailability' flow have not been updated.

Did you update these as per the documentation?

Thanks

alexc-MSFT avatar Oct 08 '20 08:10 alexc-MSFT

Hi! I had the same issue. The problem was I didn't modify the List Name under Check Team Availability Flow > Check site exists response > Check for existing requests matching URL. The Deployment Guide say:

image

But it doesn't say anything about modifying the "List Name" field. This field must be replaced by "Teams Requests", that is the List Name.

I hope it helps! Thanks!

FernandoGualano avatar Nov 23 '20 16:11 FernandoGualano

There is only the Team request Approval flow but not an Check Team Availability flow after importing the zip file? image

What did i do wrong? Thanks

eturinox avatar Nov 26 '20 23:11 eturinox

There is only the Team request Approval flow but not an Check Team Availability flow after importing the zip file? image

What did i do wrong? Thanks

The "Check Team Availability" flow is imported when you import the Power App package as it is linked to the Power Apps (Step 3: Set up Power Apps). When you import this package, you should see the following:

image

FernandoGualano avatar Nov 27 '20 17:11 FernandoGualano

I also see the badgateway error message. I have tried multiple browsers and signed-in as different Flow owners. I have deleted and recreated my SharePoint Flow connection. I have recreated the steps in the Flow where it references SharePoint, "Check if site exists" and "check for existing requests matching url". I confirmed they are pointing to the correct SPO site and in the 2nd step, the correct list on that site. I gave the user account site Owner and Site Collection Admin to the Request Teams Site I'm still getting the same error.

Update: I separated out the "Send an HTTP request to SharePoint" to its own independent flow. I still get the BadGateway error. I tried changing the Uri to use _api/web/lists/getbytitle('Documents') for testing. That worked. I got results. But _api/SP.Site.Exists is still giving an error.

ITAndy23 avatar Jul 27 '21 15:07 ITAndy23

@alexc-MSFT; I've taken a look at this and the variable for "TeamsRequestSiteURL" is being used as the input for the "Send an HTTP request to SharePoint" step. This is incorrect.

image

image

Instead; the full tenant name should be used "https://m365x765471.sharepoint.com" with no site defined. Then you get the desired "true" or "false" result and not a 404.

Hope this is useful.

Cheers.

BennySnatch avatar Jul 24 '22 19:07 BennySnatch

I still get the bad gateway error here, any ideas? image

krhoadesnh avatar Mar 14 '23 20:03 krhoadesnh