ChatGPT error: The app did not respond in-time. It may or may not have completed successfully.

Hey there @ChmieluXx! 👋

As Troy said, it’s likely only a temporary issue. Given the popularity of ChatGPT it’s possible that at the time the action was being tested the OpenAI API was experiencing a high amount of requests which caused it to run a bit slow. If an app’s API doesn’t respond within the set timeframe it’ll cause a timeout error to occur.

I did some checking and it looks like we’ve got a feature request open to increase the timeout window for the Send Prompt action so I’ve added your vote for that. I don’t have a ETA on when that would be implemented but we’ll be sure to email you as soon as it is.

If you’re on a paid Zapier plan and continue to run into this error I’d recommend turning on our Autoreplay feature. That will allow any runs of the Zap that run into that same timeout error to be automatically replayed a bit later, which will hopefully allow it to then go through ok. 🙂

Hi SamB,

thank you for the update and the efforts to extend the timeout window during live Zap runs to 15 minutes. This enhancement is indeed a significant improvement for production scenarios.

However, I'd like to bring to your attention a critical aspect regarding the testing phase. Currently, with the testing in the Zap Editor being limited to a timeout period of only 50 seconds, it's challenging to obtain the necessary data for subsequent Zaps. This limitation hinders our ability to configure the flow correctly, as the tests do not reflect the real-world conditions we have in production.

For a more effective and seamless integration process, it is essential to have a similar timeout threshold during the testing phase as in the live environment. Without this, the testing phase becomes somewhat ineffectual, as we can't fully validate the Zaps under conditions that mimic live scenarios.

Understanding the constraints and complexities involved, I still believe that aligning the testing timeout more closely with the live environment's timeout would be highly beneficial. It would enable a more accurate and reliable setup, ensuring smoother operations post-deployment.

Thank you for considering this request. Looking forward to a positive response and continued improvements.

L.

Hi.

I’m currently experiencing this in a live zap. In the zap history it shows up as an error, as in OP’s example:

“The app did not respond in-time. It may or may not have completed successfully.”

Any idea on how to ensure the zap completes?

Hi @ken.a . 

Ah, that’s really unfortunate, as I’ve got a complex zap and this step is absolutely essential.

It’s a ChatGPT Conversation with Assistant action, and it works in the Open AI Playground. It takes a while there too, but doesn’t time out and succeeds.

Isn’t it possible to extend the timeout limit? With the timeout limit, it significantly reduces the utility of Assistants, which are designed for and capable of long complex tasks. 

Also, the earlier response from @SamB says prompt completions during live Zap runs are allowed up to 15 mins to be completed before a timeout error will occur, and this error occurs well before that. So I’m confused as to why I’m getting the error I’m seeing in the first place?

This is ridiculous. A test should have the same time limit as live. how are we supposed to collect the necessary data???