Jotform API Integration with Power Automate Failing (502 Bad Gateway)

  • Javier_Vera
    Asked on April 3, 2025 at 3:31 PM

    Hi Jotform Support,

    We are experiencing a critical issue with the Jotform connector for Microsoft Power Automate. The error occurs when trying to retrieve the list of forms in order to trigger flows. This integration was working correctly until it suddenly started failing without any changes on our side.

    Issue Summary:

    Whenever we attempt to use the “When a response is submitted” trigger in Power Automate, we receive a 502 Bad Gateway error, and the form list cannot be loaded. As a result, all of our automated flows connected to Jotform have stopped working, severely impacting our company’s operations.

    Actions Already Taken:
    • Refreshed and updated authentication credentials.
    • Deleted the old connection and created a new one.
    • Verified API key permissions in Jotform settings.
    • Cleared browser cache and cookies.
    • Confirmed that the Jotform API endpoint is responding correctly via Postman.

    We kindly ask for your urgent assistance in resolving this issue.

    Jotform API Integration with Power Automate Failing (502 Bad Gateway) Image 1 Screenshot 20

  • Javier_Vera
    Replied on April 3, 2025 at 3:47 PM

    The complete Error Code is : "Could not retrieve values. No se pudo realizar la solicitud de invocación dinámica y se devolvió el siguiente error: Unexpected error occurred when 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": "default-a5199d4e-3ec4-425b-bf0a-055b4485e8df.12.common.brazil.azure-apihub.net",

      "clientRequestId": "fc466bda-6b71-4d9f-b43c-5ecb94d42187",

      "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'."

  • Jovito JotForm Support
    Replied on April 3, 2025 at 4:28 PM

    Hi Javier,

    Thanks for reaching out to Jotform Support. A "502 Bad Gateway" error in Power Automate when interacting with Jotform indicates a problem with Jotform's servers or the communication between them, not a problem with your Power Automate flow itself. This can be due to temporary server issues, network problems, or overloads on Jotform's infrastructure. Can you try testing the form again after an hour and check if the same issue persists? Can you tell us if the issue happened just recently? For testing purposes, can you try setting up the Power Automate integration on a different form and check if the same issue happens?

    Give it a try and let us know how it goes.

  • javierveracid
    Replied on April 3, 2025 at 10:58 PM

    Hi Jovito,


    Hi Jovito,

    Thanks for your reply. The issue still persists, and after some testing, it seems the problem is related to the account itself. I created a new account, and in that one, the list of forms appears correctly.

    Main Account:
    Jotform API Integration with Power Automate Failing (502 Bad Gateway) Image 1 Screenshot 30


    Test Account:
    Jotform API Integration with Power Automate Failing (502 Bad Gateway) Image 2 Screenshot 41


    The problem is not with one form.

    Regards


  • Aries JotForm Support
    Replied on April 4, 2025 at 12:14 AM

    Hi Javier,

    I also tested this on my end, and it seems to be working correctly. Check out the screenshot below:

    Jotform API Integration with Power Automate Failing (502 Bad Gateway) Image 1 Screenshot 20

    It appears to be an issue between your account and Power Automate connection to your original account. Since you already deleted an old connection with Jotform in your Power Automate and reconnected it again, I cleared your form cache as a precaution. Can you also try a different browser or clear your browser cache? It can sometimes cause issues with web-based applications, including Power Automate and Jotform.

    Give it a try and let us know how it goes.

  • dcombellack
    Replied on April 4, 2025 at 3:55 AM

    javierveracid, I am not Jotform support, just another Jotform user like yourself. We also had this issue, however it has seemingly fixed itself this morning. It would be helpful if Jotform would accept when there is an issue rather than having us try pointless things as per the advice we were given. Hopefully yours is also now back up and running.

  • Javier_Vera
    Replied on April 7, 2025 at 10:27 AM

    dcombellack, Thanks for the reach out, at least now I know these problems are not unique to us and seem to be more widespread than we’d like

    This error has only happened once, but we’ve had several similar situations before, and the best solution support has given us so far is to “clear the cache.”, so i

    All the forms’ functionality came back the next day without any modifications on our side. Clearly, this is an issue that the first-level Jotform support cannot resolve, so I’d appreciate it if you could escalate this internally, review the error logs, and try to provide a proper solution to this issue

Your Answer