Request

Response

    High Memory, GPU and Priority Pass (Beta)

    Automation API has three optional WorkItem settings in public beta:

    • High Memory (memoryGb): process a Revit WorkItem with 64 GB of memory instead of the standard 32 GB.
    • GPU (gpu): process a Revit WorkItem on an NVIDIA GPU machine with 64 GB of memory.
    • Priority Pass (priority): have a WorkItem picked up ahead of standard WorkItems in the queue. Priority Pass is available for Revit and coming soon for the other engines during the public beta.

    You set each one per WorkItem, on the existing POST /workitems request. WorkItems that don’t use these settings run on the same machines, in the same standard queue, at the same price as before.

    For an introduction, see the blog post Introducing High Memory, GPU and Priority Pass for Automation API.

    When to use each option

    High Memory

    Use it for very large or heavily linked Revit models. When a model needs more than 32 GB of memory, the WorkItem usually doesn’t fail with a clear error. It slows down and eventually times out. Use the larger machine only for the WorkItems that need it.

    GPU

    Use it for 3D view and sheet exports on large models. Light or 2D-only exports see little or no improvement, so leave them on standard machines.

    Priority Pass

    Use it for time-sensitive WorkItems, for example when a user or an agent is waiting on the result. A P1 WorkItem is picked up ahead of standard WorkItems waiting for the same type of machine (standard, High Memory or GPU). Priority Pass affects queue position only. It does not guarantee a queue time, processing time or completion time.

    Combining options

    Priority Pass can be added to any WorkItem, including High Memory and GPU WorkItems. For example, a GPU WorkItem with Priority Pass:

    {
      "activityId": "<YOUR_APP_NICKNAME>.DeleteWallsActivity+test",
      "arguments": { ... },
      "memoryGb": 64,
      "gpu": true,
      "priority": "P1"
    }
    

    For how to set each option, see Run a WorkItem with priority (Beta) and Choose memory and GPU (Beta) in the Revit tutorial, and POST workitems.

    Engine availability

    High Memory and GPU are available for Revit only. Priority Pass is available for Revit now and is coming soon for the other engines during the public beta.

    EngineHigh MemoryGPUPriority Pass
    Revit Available Available Available
    AutoCAD No No Coming soon
    Inventor No No Coming soon
    3ds Max No No Coming soon
    Fusion No No Coming soon

    To check whether Priority Pass is available for an engine, call GET engines/:id. If the response includes "priorityPass": true, you can send "priority": "P1" for that engine. If the field is absent, Priority Pass isn’t available for it.

    Until Priority Pass is available for an engine, a P1 request for that engine is rejected with an error. WorkItems sent without priority, or with P3, are not affected.

    Beta limits

    • High Memory and GPU concurrency: each client ID can have up to 5 standard (P3) WorkItems in progress at the same time on each of the High Memory and GPU machine types. A request over the limit is rejected with an error. Resubmit it once one of your WorkItems on that machine type finishes.
    • Priority Pass concurrency: each client ID can have one P1 WorkItem pending or in progress at a time. A second P1 request is rejected with an error; it is not queued. Resubmit it once the current P1 WorkItem finishes, or submit it without priority to run as a standard WorkItem. If your organization has several APS apps, each app has its own limit.
    • Priority Pass availability: if Priority Pass isn’t available for the engine, a P1 request is rejected with an error; it doesn’t fall back to the standard queue. See Engine availability, above.
    • Queue times: priority queue wait times are published on GET health/:engine/stats with the priority query parameter. For how to read queue-time data, see Introducing queue visibility for Automation API.

    Beta terms

    • Billing: High Memory and GPU WorkItems are billed at the current WorkItem rate during the public beta, with no extra charge for the larger or GPU machine. At full release, planned for early 2027, they will be priced above the standard rate.
    • Performance: High Memory and GPU capacity is limited during the public beta, so WorkItems on those machines may wait longer in the queue than standard WorkItems. Wait times during the beta may not reflect performance at full release.
    • GPU benchmarking: during the public beta, Autodesk may run a second copy of GPU WorkItems on a standard machine to measure the performance difference. The copy uses the same inputs, writes no outputs, sends no callbacks and is not billed to you. Your inputs are downloaded a second time from the locations you provided, and you may incur costs with your data storage provider.
    • Priority Pass: free during the public beta. It is expected to become a paid add-on at full release.
    • Pricing: pricing for full release is not final and will be shared before full release. Active beta users will be notified before any price increases go into effect.

    Feedback and questions

    Send feedback and questions about the beta at feedback.autodesk.com/flexiblecompute. For other help, visit the APS Get Help page.