Execute or Queue Tasks in Scheduler

Starting from Omniscope 2026.1 onwards, we are improving how the Play action works in the Scheduler.

In previous versions, running a Scheduler task or action was a blocking process - while a task was executing, the Scheduler interface was locked, preventing other users from editing or running additional tasks. This mode also had a 30-second execution limit, as it was designed primarily for testing purposes.

With the latest release, Omniscope introduces a major improvement: task execution is now a full ad-hoc execution, meaning it runs as non-blocking background execution. Multiple users logged into the Scheduler app can now execute or edit tasks simultaneously without being blocked.

You can now also continue working in the Scheduler - creating or editing existing tasks - while executions run in the background.

How It Works

When you trigger an action or task using the Play button:

1. Confirmation Step
   
   
   
2. Execution Starts
   The task begins executing or queued on the server:
   
   
   
   
   
3. Background Tracking
   
   Once sent to the background, you’ll see a message:
   
   
   
4. Execution finished
   Once the execution finishes you will see the output plus timings:

⚠️ Important Notes

• Parallel executions:
  The same task can now run multiple times concurrently (for example, one manually triggered and one scheduled).
  
  

• Avoid overlap when testing:
  If a task is also scheduled automatically, triggering it manually may start a duplicate execution.
  
  

• Improved logging:
  All executions are now recorded in Scheduler logs - including start time, user, and completion details -improving transparency and troubleshooting.