Job Queue

The Job Queue (also called the Task Queue) is the background execution system for all workflows in the MinuteView Automations Engine. It manages how and when workflows are executed — either immediately (“on the fly”) or through the background queue.

---

1. Overview

The Job Queue ensures workflows are executed reliably, even under heavy load. When workflows are run, they can either:

• Run immediately (on the fly) — processed instantly within the current automation session, or
• Be added to the queue — scheduled for background execution through the Job Queue.

This flexibility allows users and administrators to balance performance, responsiveness, and system stability across multiple workflows.

---

2. How It Works

When you execute a workflow, the Automations Engine checks its trigger type and execution settings to decide whether it should:

• Run immediately — typically for short or interactive workflows
• Enqueue for background processing — ideal for long-running or resource-heavy workflows

The queue itself runs continuously on the MinuteView Server using the same database that hosts your MinuteView Server. Once MinuteView Server is installed, the Job Queue system (internally powered by a reliable background job framework) becomes active automatically. No additional configuration is required.

---

3. Accessing the Queue Monitors

You can monitor and manage queued jobs through two interfaces:

Default Queue Dashboard

• URL: <AutomationEngine>/AutomationsQueue
• Displays the default queue monitor interface for advanced technical users.
• Shows all jobs, including their state (Enqueued, Processing, Succeeded, Failed, etc.), queue name, and retry counts.

Custom Queue Monitor

• URL: <AutomationEngine>/QueueMonitor
• Provides a clean, simplified, real-time view tailored for MinuteView users.
• Displays only essential job information and statuses.

---

4. Execution Modes

Workflows can be executed in one of two ways, depending on their trigger or configuration:

a. Immediate Execution (“On the Fly”)

Some workflows must execute instantly without waiting in the queue. These are typically used for interactive or user-dependent processes that require real-time responses.

Examples:

• Configurator Workflows: When a user interacts with the Configurator, workflow results are required immediately to update on-screen controls, pricing, or configuration options. Because of this dependency, these workflows always run instantly and never go to the background queue.

Use Case: If your workflow is lightweight, user-driven, or must produce an instant response — use immediate execution.

---

b. Queued Execution (Background Processing)

For most workflows, especially long-running or server-based automations, queued execution is preferred.

Queued workflows are added to the Job Queue and executed asynchronously by the Automations Engine in the background. This ensures reliability, better performance, and load balancing across multiple concurrent workflows.

Typical Examples:

• Large document processing
• File exports or conversions
• Vault or SharePoint synchronization tasks
• Scheduled operations (e.g. daily checks, batch imports)

Benefits:

• Frees up system resources
• Prevents timeouts on large workflows
• Allows detailed job tracking and retries

---

5. Automatic Trigger Behavior

Some workflow triggers automatically decide how the workflow is executed, regardless of user preference:

Trigger Type	Execution Behavior	Notes
Scheduled Task	Always added to the queue	Scheduled workflows must run through the queue for reliability.
Vault Job Queue	Always added to the queue	Triggered by Autodesk Vault jobs.
Configurator Trigger	Always processed immediately	Must respond instantly for interactive user sessions.
Manual Execution	Can be queued or run immediately	User chooses depending on performance needs.
API Trigger	Follows configuration	Configurable per workflow.

Best Practice: Where possible, queue your jobs to offload processing from the automation server and improve stability — especially on systems with limited resources.

---

6. Monitoring Job States

Every workflow job in the queue has a state that shows its current progress:

State	Description
Queued	Waiting to be processed by the Automations Engine.
Processing	Currently being executed.
Succeeded	Completed successfully.
Failed	Encountered an error (check logs for details).
Deleted	Manually removed or expired.

All state transitions are recorded in system logs for traceability and auditing.

---

7. Retrying and Re-Running Jobs

If a job fails:

1. Check its status and error details in the queue monitor.
2. Click Retry to reprocess the job.
3. Alternatively, re-run the workflow manually — it will be re-enqueued as a new job.

Retries are limited per workflow type to prevent loops or repeated failures.

---

8. Performance and Load Balancing

The Job Queue is optimized for stability and performance:

• Jobs are processed in batches by background workers.
• Processing delay adapts dynamically based on system load.
• Workflows are cached and refreshed intelligently to minimize redundant processing.
• The Automations Engine ensures fair distribution across concurrent jobs.

To improve performance on busy environments:

• Queue as many workflows as possible rather than running them immediately.
• Increase worker capacity (threads) if your server handles a large automation load.
• Monitor the QueueMonitor page regularly to detect bottlenecks.

---

9. Troubleshooting

If workflows appear stuck or not running:

1. Verify that the Automations Engine service is active.
2. Visit <AutomationEngine>/AutomationsQueue to check the job list.
3. Look for failed jobs and inspect their logs for error messages.
4. Restart the Automations Engine service if jobs remain idle for long periods.
5. Confirm that SQL Server is online and accessible (the queue depends on it).

---

10. Summary

The Job Queue is a critical component of the MinuteView platform. It ensures that workflows execute in the most efficient and reliable way possible — either immediately for interactive use cases or through the queue for background operations.

In short:

• Use Immediate Execution for user-driven, real-time workflows like Configurator.
• Use Queued Execution for all other workflows to maximize performance and system stability.
• Monitor job progress via <AutomationEngine>/QueueMonitor.
• Schedule jobs or heavy workflows to run in the background wherever possible.