Skip to main content

Overview

The Driver Management page shows all Windows machines connected to your organization that can run automations.

Driver List

Each connected driver shows:
FieldDescription
NameMachine identifier
StatusOnline, Offline, or Busy
IP AddressNetwork address
Last HeartbeatWhen it last checked in
Current JobActive automation (if any)
Queue DepthJobs waiting for this driver

Status Indicators

Online

Connected and ready to accept jobs

Busy

Currently executing an automation

Offline

Not connected to the backend

Driver Details

Click any driver to see detailed information:
  • Machine name and ID
  • Operating system version
  • IP address and port
  • Connection status
  • Uptime

Queue Status

See the overall job queue:
MetricDescription
Total QueuedJobs waiting for any driver
Avg Wait TimeHow long jobs typically wait
Active JobsCurrently executing
If the queue is backing up, consider adding more driver machines.

Job Assignment

Jobs are assigned to drivers based on:
  1. Availability - Is the driver online and not busy?
  2. Capabilities - Does it have required software?
  3. Priority - Higher priority drivers get jobs first
  4. Round-robin - Distribute load evenly

Adding New Drivers

To add a new driver machine:
1

Create Enrollment Token

Go to API Management and create a token
2

Install Driver Software

On the Windows machine, install the Granite driver
3

Run Enrollment

Use the token to register the machine
4

Verify Connection

Check this page to confirm it appears as Online
See the Driver Installation Guide for detailed steps.

Removing Drivers

To remove a driver from your organization:
  1. Click the driver in the list
  2. Go to Settings tab
  3. Click Remove Machine
  4. Confirm removal
Removed machines can’t run automations until re-enrolled with a new token.

Troubleshooting Offline Drivers

If a driver shows as offline:
Can the machine reach api.getgranite.ai?
Test-NetConnection -ComputerName api.getgranite.ai -Port 443
Is the driver process still active?
Get-Process granite-driver -ErrorAction SilentlyContinue
Review driver logs for errors:
Get-Content C:\granite\driver\logs\latest.log -Tail 50
Stop and start the driver service:
Stop-Process -Name granite-driver -Force
Start-Process C:\granite\driver\granite-driver.exe

Monitoring Best Practices

Get notified when drivers go offline unexpectedly.
If queues grow consistently, add more drivers.
Look for patterns in failures on specific machines.
Run the latest driver version for best compatibility.

Scaling Drivers

When to add more drivers:
  • Queue wait times exceed acceptable limits
  • You’re running more concurrent automations
  • You need geographic distribution
  • You want redundancy
When to remove drivers:
  • Reducing costs
  • Consolidating infrastructure
  • Decommissioning old machines

Next Steps