Deducting Quota for 'Server Busy' Errors? Fix Your Broken Billing Logic

Incredible business model you have here:

"Incredible business model you have here:

  1. Fail to answer simple prompts.

  2. Force the user to sit there and click ‘Continue’ almost the entire day.

  3. Spam them with ‘Server busy’ errors.

  4. Count those failed clicks to drain their entire quota.

  5. Beg them to upgrade to the ‘Ultra’ plan. I’m not paying a single cent more to a service that penalizes users for its own server downtime. Consider this subscription permanently cancelled."

can not use all of time

guys what is going on ? servers busy ? please there is no contact no

wait, every one has this issue, it repeat again and again and my billing count? the usage is gone with zero result

I feel that this should not be a business model. If they take away tokens when their servers report error, surely it can be contested in most countries. Users should not have to pay for google’s server’s errors. Users pay for a service, if the service throws an error, user should not be charged a single token’s price.
People need to be louder about this.

Prioritizing Tool Selection

I’m currently focused on how to best select the optimal tool from the available options. The overriding principle is to choose the most specific tool for each task. The related tools are at my disposal, including grep_search, list_dir, view_file, replace_file_content, multi_replace_file_content, write_to_file, and run. I’m starting to build a hierarchy of tasks to tool mapping based on specificity.

if they working, gemini also say this and do nothing