web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / 'OpenApiConnection' is...
Power Automate
Answered

'OpenApiConnection' is not valid, only when a given status is selected in Power App

(0) ShareShare
ReportReport
Posted on by 23
Hi,
I have a flow that is triggered by Power Apps.
It has a Switch card that looks at the status of the item in Power App and subsequently does a set of actions according to this status.
It works with no problem with the exception when the status in Power App is changed to be Completed.
The flow fails at Get Request action card, which is just before the Switch action card. Therefore at that moment, the Power Automate flow does not "know" that the status is Completed. 
The error says the following:
The 'inputs.parameters' of workflow operation 'Get_request' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'id' is required to be of type 'Integer/int64'. The runtime value '""' to be converted doesn't have the expected format 'Integer/int64'.
Which I translate to meaning that the Power Automate is expecting the ID of the request to be an Integer but it is not.
I don't understand why it picks up the Request ID as an Integer from Power App for any other status but not for when that item changes status to Complete.
Example:
  • ID 203 is created in Power Apps with status Created.
  • Flow triggers, goes down the Created Switch card path.
  • ID 203 is updated in Power Apps with status In Flight.
  • Flow triggers, goes down the In Flight Switch card path.
  • ID 203 is updated in Power Apps with status Completed.
  • Flow fails with above error message.
Any ideas/ suggestions would be most appreciated.
Many thanks in advance.
MROD
 
Categories:
I have the same question (0)
  • Verified answer
    MR-14090903-0 Profile Picture
    23 on at
    Hi, 
    The issue has been resolved.
    Actually, there was nothing wrong with the Power Automate flow.
    Issue was in PowerApps (not passing a value for an input parameter).
     

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 525 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 324 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard