Error message when uploading swagger definition file

[BenediktE]

Currently I always get this error message when uploading a swagger file for creating a new connection:

The request failed with error: 'Error in element 'when' on line 1, column 
1799: There is no policy matching element name'. The tracking Id is 
'69cec690-49a5-4703-9ae9-98ce6ccf5552'.

The same file worked before. What can I do to figure those problems out?

Furthermore when I try it again, I get the following message:

You have already created an api with display name 'SimplicDEFAULT'. Please specify a different name.

But there is no connection with this name. Thanks a lot!

Thanks a lot!

[JorgeGonzalez]

Dear,

Today Ive repeat the process and the error now its different

The request failed with error: 'Error in element 'set-header' on line 21, column 10: The explicit expression block is missing a closing ")" character. Make sure you have a matching ")" character for all the "(" characters within this block, and that none of the ")" characters are being interpreted as markup.'. The tracking Id is '7a90004b-7348-4bbf-8a93-6d691f818c60'.

And checking the file with the tool I don't seen any "("

Thanks

[BenediktE]

Ok, now a new error occurse:

The request failed with error: 'Error in element 'set-header' on line 21, 
column 10: The explicit expression block is missing a closing ")" character.
 Make sure you have a matching ")" character for all the "(" characters within
 this block, and that none of the ")" characters are being interpreted as 
markup.'. The tracking Id is '5f6c4747-f100-4836-83cc-89583032e24a'.

Will this be fixed too?

P.S.: the swagger file is absolutly correct.

P.S. 2: Does this fix contains connections which are not visible, but "exists" when creating new connections? For example often I get the error message that a connection exists, which are obiously not existing due to the UI. For example I can not reuse a connection name, when it an error occurse during connection adding.

[davidme]

Yes! We jumped the gun a little on declaring all-clear. Sorry about that! The issue is now confirmed resolved.

We apologize for the inconvenience this issue has caused, and will be postmorteming our procedures that led to this issue making it to the production environment in the first place.

Best regards

-David Messner

Engineering Manager, PowerApps

[BenediktE]

Thank you. The last thing that is not fixed are doublicate connection names. For example, if I've tried to add a connection with the name Foo and that failed, than I can't use this name again. Would be nice if those connections will be cleared.

Thanks a lot!

[JorgeGonzalez]

FIXED!!!!!!!!!! Its works!!

Thanks

[mob]

Seems that's ok.

keep you updated

tnx!