Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.

When importing original camera files (OCF) and audio files through Footage Backup there are a few common errors that can occur.  Below are the troubleshooting steps on how to resolve these issues. If you are still encountering errors please contact your assigned production workflow specialist. 

MHL Errors

If there is a discrepancy between the MHL of a camera roll or sound roll and the files in Content Hub Workspaces you’ll see this error condition. 


Figure A

You can click on it to review what the conflict is.


Figure B

Errors will almost always be one of the following four conditions:

Situation 1: No MHLs were found on the rolls you’re trying to import

Error Message: 


Figure C

Possible Scenarios

      • MHL Missing - There is no MHL in the selected camera or sound roll
      • MHL Wrong Location - MHL is present, but not in the root folder of the selected camera roll. 


Figure D

Suggested Action: Confirm that there is an MHL at the root folder of the roll being imported (in this case, the MHL file should be inside of ‘P002’ folder as seen resulting on the below image).

Figure E

Situation 2: Checksums of the files in the camera or sound roll being imported don’t match those stated on the MHL

  • Error message:


Figure F

Possible Scenarios: 

  • At some point files were not verified when copying them between local storage or volumes (from a RAID to a Shuttle or from a shuttle to a SAN, for example) and some files were corrupted.
      • Upload to CH made some files corrupt

Suggested Action

  1. Perform MHL validation on the problematic asset on the volume you uploaded from using a data management tool.
    • If the validation succeeds, then there was likely an error uploading.
      • Try re-uploading
      • If this does not solve the problem,  please contact your assigned Production Workflow Specialist. 
  2. If the validation fails there is likely a ‘bad copy’ in the chain, and you should 
      • work with the teams responsible for managing data to find at which point the correct data was corrupted 
      • copy that healthy data to the upload storage using some form of checksum verification.
      • Upload the healthy data to Content Hub Workspaces and import the healthy data following the regular import procedure.

Situation 3: On the roll being imported there are some files that, when compared with the roll’s defined MHL, don’t have a corresponding checksum   

Error message:


Figure G

Possible Scenarios: 

      • An 'extraneous report' was generated by the copy tool and it’s not stated on the mhl.
      • 'Extraneous files' were added to the roll after the MHL was generated therefore the extraneous files lack a checksum on the MHL.
      • There were various offloads of the same roll on set and the copy tool did not update the mhl.

Suggested Actions

  1. Identify what file is missing on the MHL 
  2. Trace back the history of that file and try to answer the questions ‘when was this added’ and ‘why is it not on the MHL’.
  3. If there is no clear answer, please share the source folder of the project with your Production Workflow Specialist through workspaces for them to advise.  

Situation 4: Some files listed on the MHL cannot be found. .

Error message:


Figure H

Possible Scenarios:

  • A local copy was not completed but the MHL was copied, resulting in the MHL containing more checksums than files exist in the roll
  • The MHL is defining folder paths that aren't relative to where the MHL is located
  • Folder names have been changed after MHL was generated
  • Files have been renamed after the MHL was generated

Suggested actions: 

  1. Identify what is the root cause of this problem.
  2. Track back to when the problem was introduced. 
  3. Get a healthy copy of the data and try to import again.
  4. If these issues are still present, please share the root asset folder with your Production Workflow Specialist for them to advise.  



If there’s a discrepancy between the folder structure and the profile selected this screen will show up. 


Figure I

Possible scenarios:

  • The correct import profile was not selected upon import
  • The folder selected as the ‘Source’ does not match the profile selected
  • Shoot day in the shoot date/day folder name is missing
  • A Camera_Media or Sound_Media folder does not exist within the shoot date/day folder.

Suggested actions: 

  1. Make sure the correct import profile is selected.
  2. If the correct import profile is selected make sure that the correct source folder is selected. For instance on the Netflix Recommended profile, the expected source folder must be one level up from the shoot day.
    Footage_Trouble_J.pngFigure J
  3. If the correct source folder is selected for the correct import profile, it means that there may be a discrepancy in the rest of the folder structure. Please come back to workspaces and check again that the folder structure matches that defined on the import profileIf it doesn’t, correct the folder structure to match the import profile.
  4. If the issue is still present after fixing, please share the source project’ folder with your Production Workflow Specialist for them to advise. 
  5. If you have a custom folder structure that you would like to get support for, please reach out to your Production Workflow Specialist.


Some recommended data management tools are:

  1. Pomfort Silverstack 
  2. Yoyotta 
  3. Hedge
  4. Shotput Pro
Was this article helpful?
0 out of 0 found this helpful