Using the perform Task action you can use the %priority variable with math, "%priority+1". Among other controls you have the Task Properties "Collision Handling".
I think this is due to the fact that Tasker just places these new tasks at the back of the queue,
Use the run log to determine the exact cause of the delay.
Menu / more / run log
You will need to work out which task(s) are running and which require higher priority.Using the perform Task action you can use the %priority variable with math, "%priority+1". Among other controls you have the Task Properties "Collision Handling".
Menu / more / run log
Always worth checking the user guide. The explanation is far superior than I could achieve.
tasker.dinglisch.net/userguide/en/tasks.html
I tried setting the priority like you showed, but it didn't change anything.
Sorry, that wasn't a solution just a indication of your options. As Rich stated, use of the run log is important in figuring out the issue.
As for collision handling, my understanding is that this only handles things when 2 of the same task are running?
One option could be when using the notification click perform the same running task to kill the existing task - you have local variables available to you such as %caller() and %evt_prm().
With perform task, yes. Otherwise tasks have set priorities depending on where they originated. See the user guide.
I just have a string of tasks, one leading to another with 'perform task', without relying on profiles to start them based on context. These tasks create notifications all of the same name so one replaces the other, but they all have a button that should stop any running tasks. I created a seperate task for this, that should start whenever I click the button in the notification. I can set the priority for this from within the notification, but it doesn't seem to change anything, it'll only start when the currently active task has ended.
Without going into detail on your particular setup, try using perform task from the notification click with a set priority of 50 (press the arrows and use the slider).
If it's a completely separate task from those that are running and it has a higher priority it should take priority over the others.
Put a beep as it's first action, good for troubleshooting.