GoToWebinar Flow - Add New Registrant to Excel BAD REQUEST

[jmaurer]

I've been running a flow for a few weeks that adds a new gtw registrant to an excel file. Recently, it has stopped working, giving me a BadRequest Error. The only message in the output is: 

{ "Access-Control-Allow-Headers": "origin,x-requested-with,authorization,accept,content-type", "Access-Control-Allow-Methods": "GET,POST,PUT,DELETE", "Access-Control-Allow-Origin": "*", "Access-Control-Max-Age": "3628800", "Timing-Allow-Origin": "*", "Date": "April 2017", "ETag": "\"89589599d08d\"", "Server": "Apache-Coyote/1.1,Microsoft-HTTPAPI/2.0", "Content-Length": "0" }

I would expect a server response such as 400, 404, 500, 503... can anyone provide help?

[v-yamao-msft]

Hi Jmaurer,

To test this issue, I create a similar flow to insert Excel row when a registrant is added in GoToWebinar.

I don’t run the flow for many times so I am not able to reproduce your error on my side.

 

Do you have any limitation on your Webinars? Such as the number of the registrants.

Could you try to Resubmit the flow that has failed?

You could also try to recreate the connection to see if it works.

Best regards,
Mabel Mao

[jmaurer]

Thank you for your reply.  I have previously tried to 1) recreate the connection to GoToWebinar and 2) delete and recreate the flow to no avail. As of this morning, I am still receiving the same error. 

There is no limitation on the webinar in question. Also, I used a web app and some python to pull the data from G2W API using the same credititals provided in the flow so I assume the issue lies on the flow end of things. Does MS Flow have a limit to the number of G2W API calls that can be made?  I've probably successfully added a registrant from the API over 200 times via FLow. 

My organization is very excited about the automations that can achieve via MS Flow, but have noted a few frustrating inconsistancies. I understand it's still a young product that is begining to scratch the surface of office/data flow automations so I will continue to advocate for its uset; however, patience with software is not always easy to defend. 

[jmaurer]

For anyone keeping up with this issue... I tried reconnecting to GoToWebinar again and this time had a row added to Google Sheets. Unfortunately, I get the same error response:

{ "Access-Control-Allow-Headers": "origin,x-requested-with,authorization,accept,content-type", "Access-Control-Allow-Methods": "GET,POST,PUT,DELETE", "Access-Control-Allow-Origin": "*", "Access-Control-Max-Age": "XXX800", "Timing-Allow-Origin": "*", "Date": "Tue, 25 Apr 2017 16:11:18 GMT", "ETag": "\"e587924622e83dd\"", "Server": "Apache-Coyote/1.1,Microsoft-HTTPAPI/2.0", "Content-Length": "0" }

Hopefully this gets worked out...

[jmaurer]

Trying to keep folks updated. I have let the Flow continue to run and fail.  For the most part, repeats the same error message as previously provided in this thread.  However, i did catch one that was diffferent.  This error message actually provided a body:

{ "errorCode": "AuthFailure", "description": "The credentials supplied are not valid.", "incident": "5039386528445966091" }

Again, I know the creditentials are fine. I used the same ones to generate a token which is used in python script to grab data from the api.  

My organiztion has several business use cases for Microsoft flow, but we've experienced several inconsistances with the product. GoToWebainar has proven to be the most problematic, but other flows have intermittently failed and provided poor messaging.

I remain an advocate for the product and think that Power Apps/Flow/PowerBI can evolve in to a great ecosystem for us.  

[Drix]

@jmaurer  were you able to figure it out? Thanks!