Gemini users hit chat loading, memory, and workflow problems

On June 30, 2026, during U.S. Eastern time, the Gemini app opened its home screen but failed to load the chat list, showing a “couldn’t connect, try again” message. The service later came back, but the same period also showed wider frustration with Gemini’s reliability.

Custom Gems sometimes reset after only a few replies, forgot the earlier conversation, and asked the starting questions again. Long chats could get stuck with Error 1152, and a workaround claimed that sending the prompt through a different modal API path could restart the stuck connection without deleting the chat history. Other complaints focused on Gemini forgetting recent discussion, missing uploaded documents, giving hallucinated answers, or blocking generation in Flow after only small prompt changes.

There was also a positive side: Gemini and DeepSeek helped set up a Python virtual environment, install LM Studio, configure SUID permissions, install libraries, edit Python scripts, and get a local AI model running. A separate scare involved an unknown prompt asking Gemini to search Gmail and summarize an upcoming Japan trip, which raised concerns about account connections, permissions, and personal data.