Several forms losing integration with Microsoft Flow

Dear Sir/Madam, good afternoon.

We have several JotForm forms that frequently lose integration with Microsoft Flow.

To fix this, we are deleting the API key (Microsoft Flow) and creating a new one at:

https://www.jotform.com/myaccount/api.

Is there any routine or process on your end that might be causing us to have to redo our integration?

I ask because this is the second time in less than 15 days that this error has occurred.

Please see the previous ticket we opened regarding the same issue:

Tickets: 1 - https://www.jotform.com/answers/25864641-try-to-create-integration-with-flow

Below is the error returned by Microsoft Flow:

calling the ApiHubsRuntime API: 'Microsoft.Azure.ProcessSimple.Data.Entities.Exceptions.ProcessSimpleDataException: The ApiHubsRuntime API call failed with http status code 'BadGateway' and response content '{

"error": {

"code": 502,

"source": "msmanaged-na.azure-apim.net",

"clientRequestId": "560290e1-7be4-44b4-9f5a-15cb4f56a026",

"message": "BadGateway",

"innerError": {

"message": "https://api.jotform.com/docs#vid-user-forms"

}

}

}'

at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass51_1`2.<<CallService>b__0>d.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 693

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<CallService>d__51`2.MoveNext() in C:\__w\1\s\src\processsimple\Roles\ProcessSimple.Data.Shared\DataProviders\Services\HttpClientDataProvider.cs:line 530'.

Hi Sistemas_Movida,

Thanks for reaching out to us for help. When you say this is the second time in less than 15 days, may we know how you fixed the issue on the first one?

Try disabling the login requirement when opening file submissions. It's easy to do. Let me walk you through it:

1. Login to your Jotform account on your Desktop (it's not available yet on the Mobile App).

2. Click on your Avatar/Profile picture on the right side of the screen, and click on it.

3. In the dropdown, click on Settings, or click on this link to go directly to your Settings page.

4. Now, go to the Security tab and uncheck the box next to Require Login to View Uploaded Files under the Privacy section.

After that, give it a try and let us know if you need any other help.

Good morning Jan, how are you?

The first time, we were able to solve the problem by removing the Microsoft Flow key and creating a new one. I believe this is not the correct procedure, and besides that, we have to recreate all the flows in Microsoft Flow.

I have a question — the procedure you’re suggesting (enabling the parameter: Require log-in to view uploaded files) — does it prevent the error from happening, or is it more of a precaution to avoid this scenario in the future?

Thank you.

Hi Sistemas_Movida,

I'm doing well, thank you. How are you?

I see, creating a new Microsoft Flow Key fixed the issue. Thanks for sharing that information. Unfortunately, we have lots of users using Microsoft Flow and they're not experiencing the issue. That's the reason, I asked to disable the Require log-in to view uploaded files to narrow down why the issue on your end keeps happening.

Some of our integrations are not working if the Require log-in to view uploaded files is enabled. Another one is by reaching the API limit per day. Can you check how many API calls/request do you consume per day? The Gold level have 10,000 requests per day.

Once we hear back from you, we'll be able to help you with this.

Dear Jan,

The parameter "Disable the 'Require log-in to view uploaded files'" is not enabled, so I believe that is not the cause.

As you can see, we are within the limit, but even if the limit had been exceeded, is it correct that our flows lose connection with Microsoft Flow?

Could you verify which parameters need to be enabled so that the integration with Microsoft Flow can work without errors?

Regards

Hi Sistemas_Movida,

Could you share with us the API used and your Microsoft Flow configuration so that we can check it out on our end? The API Key shouldn't expire and should allow you to access contents when regardless of your account Security setting if the permission is set to Full Access.

Once we hear back from you, we'll be able to help you with this.