themrlawrence
commented
11 months ago I am having the same issue as well. Here is the workaround that has been working for me (so far):
- When the response is interrupted due to an error (e.g., {network error}), refresh the page in your browser[^1] – do not regenerate the response.
- The "Regenerate" button will have disappeared, and you will be able to enter a new message prompt.
- Give AutoExpert the prompt, "Please continue."
It will then continue from where it left off.
[^1]: I'm paranoid about losing chat context, so before I refresh the page, I copy the response that was interrupted and paste it into an editor (I use MarkText and Obsidian). That way, if the response isn't there after refreshing the page, I can provide the response to AutoExpert and ask it to continue where it left off.
github-actions[bot]
Edition
Check one or more:
Good afternoon, I know this is an issue with Chat-GPT as a product, but when using the Dev edition of your Custom GPT. When responses get rather long, when analyzing exisiting code. It will timeout, I have tried a view different ways to get past this such as asking it not to provide a description of the code and to just debug. It seems to continue to time-out. I was unsure if this was simply a limitation of GPT's or something i should make you aware of so i wanted to make an issue incase is was unintended. I can provide any additional information if needed.