Bug: Jobs Fail if Temp Directory Is Not Accessible From Shared Storage

[olly-glenn-arch]

Describe the bug

When a the submitter creates a job bundle, it writes out certain files (such as create_output_directory.py and fonts) to the user's temp directory. If the farm is not configured to use job attachments and the temp directory is not located on shared storage, the worker cannot access it and the job will fail.

This is happening in a Customer Managed Fleet that exclusively uses shared storage (no job attachments).

Expected Behaviour

Files generated for the render are copied to a shared directory that workers can access.

Current Behaviour

Files generated for the render are copied to the user's local temp directory, which is not always accessible to render nodes.

I've attached logs from the failed job. D: is the local storage, P: is the shared storage.

FNM-MPG_FNM MAIN_session-9f967a4ae411451ba0125e1db195eed9.log

Reproduction Steps

1. Make sure that job attachments are disabled
2. Create an After Effects project on shared storage that is mounted to both the local workstation and the workers
3. Make sure that the user's temp directory is not located on the shared storage
4. Submit a render job from the project

Environment

At minimum:

1. Windows 2025
2. After Effects 25
3. Deadline 0.53.0

D: is local storage and is where the user profiles are stored, P: is the shared storage that the render nodes can access.

[viknith]

Thank you for submitting this issue! We will take a look and get back to this issue once prioritized.