This happens when you refresh a database from your prod instance to a test instance, and that test instance inherits key system properties that tell export jobs where to send files.
Check the system properties page for all your front-end instances to see where each instance is configured to send files. If any instance points to the live directory, change it. For more information please see: Changes to system properties
You might also see this issue if you’re getting 0kb files. Even if files were exported in the prod instance when the cycle completed, after the refresh those cycles might’ve been in a completed-but-unexported state. Or they were generated during testing on the test instance, which you’ve identified as pointing to the wrong directory.
If the issue persists, raise a new case with these details:
The file you received.
The cycle ID it came from.
The instance (if known).
A detailed description of your situation.