I can't save personal content for gem-bot

When I try to save, I get a completely uninformative message: “Something went wrong.” Region: Vietnam, Operating System: Windows, Browser: Chrome
Version: 144.0.7559.97 (official build) (64-bit)

Dear Albugankov,

I understand your frustration with the generic error message “Something went wrong.” (3) when trying to save your personal context for the Gem-bot. Such messages are indeed challenging because they offer no clues about the root cause of the problem.

While the Google team works on providing more specific error messages, here are some steps you can try to better diagnose the issue and provide additional information that might help accelerate its resolution:

  1. Try Again:
  • Sometimes, generic errors can be transient. Try saving again after a few minutes.
  1. Check Your Internet Connection:
  • Ensure your internet connection is stable and working correctly.
  1. Test in Another Browser or Incognito Mode:
  • Try to reproduce the error in a different browser (e.g., Edge, Firefox) or in Chrome’s incognito/private browsing mode. This helps rule out issues with browser extensions or cache/cookies.
  1. Reduce Content Length:
  • If the “personal context” you are trying to save is very long, try saving a smaller, simpler piece of text. There might be a character/token limit that is not being explicitly stated. Saving a short and simple text can help identify if the problem lies with the content itself or with the saving functionality.
  1. Check the Developer Console (F12):
  • Important Step: Before attempting to save, open your browser’s Developer Tools (usually by pressing F12 ).

  • Navigate to the “Console” and “Network” tabs.

  • Attempt to save again.

  • Observe if any red error messages appear in the console or if any requests in the “Network” tab fail with an error status (e.g., 4xx, 5xx). This technical information is extremely valuable for the development team. If possible, take a screenshot or copy these messages and paste them into your forum report.

  1. Record a Short Video (if possible):
  • If feasible, record a short video showing the process from the start of editing until the error message appears. This can reveal visual details that are difficult to describe in text.

Essential Information to Include in Any Future Report:

  • Exact Content: If you can isolate that the error occurs with a specific text snippet, share that snippet (if it’s not sensitive).

  • Console/Network Screenshots: Information from the Developer Tools is the most valuable for the technical team.

  • Precise Reproduction Steps: Describe exactly what you did before the error occurred.

I hope these tips help identify the cause or, at the very least, provide more concrete data for the Google team.

Unfortunately, this isn’t related to the length or browser or internet connection issues; it simply doesn’t work. I periodically get the same error when I’m just chatting with gem-bot and trying to send a message: “Something went wrong (2)” and the message simply doesn’t send.

1 Like