Thank you once again for your prompt response; I truly appreciate it. In order to facilitate easier and more secure testing (debugging), I’ve attached the Python code to my assistant in the playground. Overall, it seems to be functioning adequately, at least in terms of saving files. However, I’ve noticed a few discrepancies between this version (v2) and the previous one (v1) that I’d like to address and share with the community:
- When attaching a content file for search in the vector store along with the Python code to the code interpreter, the assistant seems to be mixing up the files, even after being called by file ID, which results in an error. It appears that the code interpreter is attempting to load the content file and is encountering an issue with its size, deeming it too large.
- The assistant is not consistently outputting the full edited content as assistant_output; sometimes, the edited text is truncated. I’ve been unable to identify the root cause of this issue.
- When Assistant B attempts to load the output file of assistant A by ID, it’s not located within a vector store but rather in the folder /mnt/data/. While file retrieval was straightforward previously, I now need to determine how to load it again in Assistant B, whether from the vector store or directly from /mnt/data/.