Troubleshooting

Most Forge issues fall into a small number of categories. Check these before contacting support.

Common Causes

Permissions

Forge needs read access to source media and write access to the output directory. If a job fails immediately with a permissions error, verify both paths in Finder using Get Info.

On macOS, Forge may also need explicit approval under System Settings > Privacy & Security > Files and Folders.

Paths

Forge does not resolve aliases or symbolic links. Use direct filesystem paths. If a source file has been moved or renamed since the job was created, the job will fail.

Network volumes must be mounted and accessible at the time of job execution. Forge does not wait for volumes to become available.

Unsupported Media

Standard mode (FFmpeg) cannot decode RAW camera formats. If you need to process BRAW, R3D, or ARRIRAW, switch to Pro mode with Resolve Studio installed.

If a format is unsupported, the job will fail with a codec-level error in the manifest.

Disk Space

Forge checks available disk space before starting a job. If space is insufficient, the job will not start. Ensure your output drive has adequate free space for the expected output size.

Support Requests

If the issue is not resolved by the above, contact support via the Support page. Include:

• The .manifest.json file for the failed job
• macOS version
• Forge version (shown in the app menu bar)
• A brief description of what you expected vs. what happened

Do not include source media unless specifically requested.