Change "Blocking" of triggers to "Background"/"UI"/"Blocking"

[ghbm-itk]

Instead of a binary blocking or not it should be possible to set 3 different types on a trigger.

I propose:

• Background task
• UI task
• Blocking task

A background task is not blocking at all. This could be a task that is pure sql or api based. These don't affect other tasks.

A UI task has to access UIs with mouse and keyboard. Two UI tasks can't run at the same time.

A blocking task needs to have the working machine for it self for whatever reason. All other tasks are blocked while this is running.

[hbpe-aarhus]

What could be an example of a blocking task? Just trying to understand the motivation between differentiating between UI and blocking.

I suppose to allow a UI trigger to run alongside a background trigger?

[ghbm-itk]

Yes the main purpose was to make "blocking" more nuanced.

An example of a blocking process could be a process that changes global state. Such as a process that changes credentials in OO.

Hmm but then it should be blocking all triggers on all machines...

I mostly just wanted to keep the exisiting functionality in case someone needs it.

[hbpe-aarhus]

How strict is blocking today? Is it fully blocking as in not allowing a non-blocking trigger to run at the same time?

Can multiple background tasks run in parallel alongside a blocking trigger on the same Scheduler?

Just some questions for clarification.

At any rate, I definitely like that non-blocking is even an option today.

[ghbm-itk]

Today blocking means that no other trigger can run on the same machine before the blocking process is done.