Although the model is responding well, sometimes a sent file gets stuck in memory, for example: I sent a file Called mem_up1.txt I ask for a report and receive the Response , but when after a while I send another file, mem_up2.txt and ask for a summary it fetches previous parameters and content, The temporary solution was to change to the flash t 2.5 model, to free up the memory. Some things disappeared, generating an empty query error. It would be interesting to inform the user what disappeared, which document, etc.Filters are sometimes not being obeyed even when deactivated. I don’t know if some of these failures were caused by the global instability of the internet but yesterday 06-12 it was slow, the model was kind of crazy,I know that high latency can affect responses, I thank the experts and the space provided.
Hi @ExuCaveira_666 ,
Thank you for providing such a detailed explanation of the issue. The behavior you described—where previously submitted files remain in memory and interfere with subsequent uploads—highlights an important challenge with context management. Your temporary solution of switching to the flash 2.5 model to clear memory is a practical workaround and may be helpful to others encountering similar problems.
Your suggestion to notify users about which documents or data were removed or retained would indeed enhance transparency and usability. Additionally, noting potential latency or instability factors is valuable feedback for both users and developers.
Thank you once again for sharing your experience.
Hi @ExuCaveira_666, @Shrushti_Patil
Thank you both again for your thorough feedback. Sharing your experience and workarounds helps the community and provides valuable input for the developers to address these bugs. If you notice any patterns or additional details, please continue to update the thread.