App Builder: Request timeout When Editing App

Every time we go on to edit our app within Jotform, the task bar just circles for 10 minutes then gives us an error page saying that the session timed out. We have tried to get you guys to address this issue last week and nothing has helped. Please fix this today. There are important updates that need to be made and this issue is holding us back.

Hi Aaron,

Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.

Let me help you with that:

From what you described, the issue happens specifically when you try to open your app in App Builder to edit it, where it keeps loading for several minutes and then shows a session timeout page. The information available only covers how to work with apps once App Builder is already loaded (changing layouts, disabling/deleting apps, letting users edit submissions, etc.), but it does not include any steps or guidance for resolving loading or session timeout issues in App Builder itself.

Because of that, there are no documented steps I can provide from the available information to directly fix this loading/session timeout behavior in your account or app.

To move forward, it would be helpful if you could share a bit more detail so our support team can investigate on their side, for example:

• Whether this happens with all apps or only with a specific one (like your “P&H Vault” app).
• Whether you see the same issue in a different browser or in a private/incognito window.
• Whether other users in your organization experience the same behavior.

Once we hear back from you, we'll be able to move forward with a solution.

Reach out again if you need any other help.

Hi Aaron,

We understand that it’s disappointing that this hasn’t been resolved yet. We take your feedback to our previous response very seriously and want to assure you that we're here to help you every step of the way, and we’re committed to finding a solution.

I tested your app and had the same issue, so I created a ticket and escalated this to our Developers. Although we don't know exactly when it'll be fixed, we’ll circle back to this thread when we have an update. 

Hi aaronharmon,

Thanks for patiently waiting while we were looking into it. I've just heard back from our Developers team that the issue should now be resolved. I've gone ahead and tested it on my end to see whether the issue still persists, but everything seems to be working properly.

Can you give it a try and let us know how it goes?