Revit jobs on the Automation API now start faster during peak usage.
Your Revit jobs now start sooner, even during peak demand. We've added pre-provisioned capacity, so jobs no longer wait in a queue for servers to start up. Nothing changes in your workflow or your pricing.
(Automation API lets developers run Revit, AutoCAD, Inventor, 3ds Max, and Fusion plugins and workflows programmatically in the cloud on a pay-per-result basis.)
What does this mean for you?
- Lower queue wait times during peak usage. When many Revit jobs arrive at once, more capacity is ready to pick them up, so jobs spend less time waiting.
- No code changes. No new parameters or endpoints, and no change to how you submit Revit WorkItems.
- No pricing change. This is a reliability improvement on the infrastructure side.
Why the change?
Revit automation often arrives in bursts, with many jobs submitted at roughly the same time. Bringing more capacity online takes a short time, and during that window, jobs can wait in the queue. This start-up delay was the most common source of queue feedback from Revit developers, and this capacity increase addresses it.
How it works
We keep a pool of Revit machines on standby, provisioned and running. When a burst of work arrives, it runs on an available machine instead of waiting for new servers to start up.
What's not changing?
The same endpoints, the same WorkItem submission flow, and the same pricing all stay in place. There is nothing to migrate and nothing to opt into.
Where to reach out for support?
We'll continue improving the speed and reliability of Revit automation. For questions or feedback, visit the APS Developer Forums.