cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
hngdev
Resolver II
Resolver II

Custom APIs result in Resource Not Found

Hello,

 

I am using Custom APIs for my app. What happens is that:

  • I had an old version of the api app and swagger file, they work well with the app
  • Then when I add new functions to the api app and update the swagger file.
  • The old functions works, but the new ones don't and result in Resource Not Found
  • I tested with web version of the PowerApps, it doesn't work as well
  • I tested API app on browsers, they all work.

Does cache involve into this? I already clear it by using Windows's Disk Cleanup and it doen't help

Anyone has any idea?

 

 

7 REPLIES 7
v-yamao-msft
Community Support
Community Support

Hi Hngdev,


How about deleting the old connection and re-creating a connection with Custom Apis? please try if this works.

 

Best regards,
Mabel Mao

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thank you,

Unfortunately, it didn't solve the problem.

yukonn
Advocate III
Advocate III

Hi,

 

Spoiler
• I tested API app on browsers, they all work.

Do you mean PowerApp application or Swagger UI?

 

 

Regards,

It happened to my PowerApps application.

Thing I figured out is that I named the connections the same for the old and new custom APIs, and I think there're some kinds of caches that stored the old one. When I changed the connection's name, it just worked.

taufik
Regular Visitor

Did your problem solved?

 

1. Sometimes when microsoft update the powerapps platform the api custom connection is affected (experience it 4 times)

2. Can you show or send me personally the swagger file? (hard to imagine what is wrong)

 

If you are not using HTTP, you are not in the cloud.

Look like bug on cloud. I face with same issue (API) is not update after add the new func. or amend on existing. What i did

 

1. Remove Existing Connector on PowerApp, Save and exit PowerApp.

2. Delete and Load Latest API to cloud.

3. Add back Connector to PowerApp.

4. Run PowerApp but still using previous Connector.

 

But it effect if we use with new name.

 

Regards,

Thank you, yukonn,

Another way to look at it.

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Power Apps June 2021

June Power Apps Community Call

Did you miss the call? Check out the recording here!

Top Solution Authors
Top Kudoed Authors
Users online (12,605)