Setting up a Vault Job Processor

Though the Job Processor is a very simple product to get up and running, a few small tweaks to the setup can make a huge different to its daily running. Here are some common tweaks we make when implementing a Vault Job Processor.

Dedicated Job Processor User

This is a frequently overlooked step in the setup of a Job Processor. Using a dedicated Job Processor user allows better logging against Vaulted documents. It also ensures that the admin account is kept as the highest level user, whilst the Job Processor receives appropriate permissions to Vault files. Is there is ever a password leak, this keeps the admin separate, and allows a quick change of password against a lower level user.

Start on Windows Logon

When using a local Job Processor, it can be cumbersome starting it every time a job gets added to the queue. This can easily be resolved by entering the administration settings within the application, and ticking Start on Widows Logon. This will add an additional product to your start-up routine, which could slow it down. However, in most cases we find this easier than starting it manually when it is required.

Restart Timing

The Job Processor pings the Vault Server every 10 minutes for new jobs by default. This can be reduced in the config files. We would recommend anything between 2 – 5 minutes if you have a high spec, dedicated machine for Job Processing.

To access the config file, navigate to C:\Program Files\Autodesk\Vault <Version>\Explorer

This will look slightly different depending on the version you have installed. For 2026, there is a JobProcessor.dll.config file.

2025 and earlier have a JobProcessor.exe.config file.

Right click on the respective config file and edit in either notepad or another text editor.

Search in the config file for the <appSettings>, against the PeriodInMinutes, set the value to your designed frequency.

Then you just need to save and restart the Job Processor.