Request for Box Support/Engineering attention: inconsistent file-operation behavior
I’m doing a structured archival migration into Box and have encountered inconsistent behavior with file operations that is making it impossible to safely verify transfers.
I’ve experienced:
-
Upload operations failing unexpectedly.
-
An upload endpoint returning an error indicating that the requested function was unavailable.
-
Move operations appearing to fail without reliable confirmation.
-
Other uploads subsequently succeeding normally.
This isn't simply a question about how to use Box. The problem is determining whether file operations are actually completing reliably and how to verify them without risking the original source files.
Because this is an archive containing authoritative source material, I am retaining every original until each transfer can be independently verified.
Could a Box employee or technical support representative please acknowledge this and advise whether there are any known issues affecting uploads/moves, account-level limitations, or integration/API operations?
If necessary, I would appreciate this being escalated to the appropriate technical team. I can provide specific examples, timestamps, filenames, and error messages.
I’m primarily looking for a human technical contact who can help determine what is actually happening on the Box side.