Maya scene file removed after cancelling USD save during Incremental Save

[jufrantz]

Describe the bug

The current Maya scene file is deleted from disk after cancelling the USD files save during Incremental Save.

Steps to reproduce

1. Open an existing Maya scene that contains a proxyShape created from an existing USD file.
2. Verify the scene file exists on disk:

   fileLocation = maya.cmds.file(q=True, location=True)
   print(f"# File exists: {maya.cmds.file(fileLocation, q=True, exists=True)}")
   # File exists: True

3. Modify a file-backed USD layer (e.g., the root layer) so the stage becomes dirty.
4. Ensure the save dialogs will appear:

   maya.cmds.optionVar(iv=("mayaUsd_SerializedUsdEditsLocationPrompt", 1))
   maya.cmds.optionVar(iv=("mayaUsd_ConfirmExistingFileSave", 1))

5. Trigger an incremental save via File > Increment and Save, or File > Save Scene with Incremental Save enabled.
6. In Save USD Options, choose Save the Maya scene file and USD files and click Save.
7. When the confirmation dialog appears, click Cancel.
8. Verify the scene file again, it has been removed:

   fileLocation = maya.cmds.file(q=True, location=True)
   print(f"# File exists: {maya.cmds.file(fileLocation, q=True, exists=True)}")
   # File exists: False

Expected behavior

Clicking Cancel should abort the save and leave the original Maya scene file intact.

Environment

• Rocky Linux 8.10
• Maya 2026.2
• Maya USD dev @ 386b4fd
• Pixar USD v24.11

[wallworm]

Thank you for reporting. We'll look into it.

[santosg87]

Hi @jufrantz,

thanks for reporting this. I did a bit of testing on the issue, and it seems we have a bit of an odd behavior here. when following the steps, i can reproduce the issue you describe - however, it seems we are losing the file on cache/the file name, but the file remains in disk.

on my testing, i noticed the same results on the python script, returning false when trying to print the file location, but looking at the file location on the browser shows my file was still there. I did notice that the name of the file changed, and the new name was not existing. this seems to be a bug with the pop-up dialog itself, where the "cancel" button seems to cancel the saving operation, but the file rename has already happened by the time the operation was canceled, so no file is saved, but the file name is now mismatched until a proper save happens.

That seems to be also the cause for your issue, I believe.
When looking at the file browser, is your original file still in disk? if so, I believe you should be able to reproduce this issue even without the incremental save.

Cheers!