Forge Viewer Model Derivative API：NWD转SVF失败求助

Hey there! It looks like you’ve nailed all the foundational steps to get your NWD file into Autodesk Forge—registering the app, securing tokens, creating a bucket, uploading the file, and submitting the translation job—but hit an internal snag during the conversion process. Let’s walk through the most likely fixes for this issue:

1. Validate the Source NWD File #

First, rule out problems with the file itself:

• Check for corruption: Open the NWD in Autodesk Navisworks to confirm it loads without errors, displays all elements properly, and doesn’t crash the app. Corrupted files often fail translation silently.
• Confirm version compatibility: Forge supports most recent Navisworks versions, but extremely old files (pre-2018, for example) might have compatibility gaps. Try saving the file in a newer, stable Navisworks version (like 2023 or 2024) before re-uploading.
• Simplify complex models: If your NWD includes heavy external references, custom plugin-generated content, or overly large datasets, this can overwhelm the translation worker. Test with a stripped-down version of the file (remove unnecessary refs/elements) to see if conversion succeeds.

2. Adjust Translation Job Parameters #

Your job request includes both 3d and 2d views—but some NWD files don’t contain valid 2D sheets, which can trigger internal failures. Try modifying the job payload to only request 3D views:

{
  "output": {
    "destination": { "region": "us" },
    "formats": [
      {
        "type": "svf",
        "views": [ "3d" ]
      }
    ]
  }
}

Re-submit the job with this payload and check the status again.

3. Retry the Translation Job #

The TranslationWorker-InternalFailure error can sometimes be a temporary glitch with Forge’s backend services. Wait a few minutes, then resubmit the translation job using the same URN—often a retry resolves transient internal errors.

4. Explicitly Set the Correct Content-Type #

While Forge can infer file types from extensions, explicitly setting the right contentType during upload helps avoid misclassification. When uploading the NWD file, use application/vnd.autodesk.nwd instead of application/octet-stream:

# Example curl command (adjust tokens/bucket details as needed)
curl -X PUT "https://developer.api.autodesk.com/oss/v2/buckets/YOUR_BUCKET/objects/YOUR_FILE.nwd" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/vnd.autodesk.nwd" \
  --data-binary "@Z2_07_85_FULL.nwd"

If none of these steps work, you can also check if there are ongoing service outages affecting Forge’s translation workers.

内容的提问来源于stack exchange，提问作者vivek shukla