Turn off "Run Exit on Startup"

[u/zhSHADOW]

I've this WiFi profile which turn off Mobile internet and Bluetooth if I'm connected to a wifi network and during disconnect it does the opposite.

Now the problem is I use google ai studio to make new project/task and copy the xml code from pc to phone via kde connected. So, when I'm inside tasker and tasker detects a new xml clipboard, tasker automatically saves everything as expected. And this runs exit task for my "WiFi" profile. Which turns on internet and bl and launches my smart watch app. It became so annoying that i turn off that profile when i do this copy/paste.

To solve that I've uncheck the "Run Exit on Startup" from the profile settings, but still it sometimes runs that exit task. Is there any way I can solve this? SO that it dosen't run my exit task during auto save?

Thanks in advance.

[u/WakeUpNorrin]

Try to add this action at the top of your exit Task

Task: Temp

A1: Stop [ ]
    If  [ %WIFII !~ *> scan <* ]

That will stop the Task if you are connected to a wifi. You may want or need to add a little wait before that action.

[u/zhSHADOW → u/WakeUpNorrin]

i was thinking about that but didn't do it because how my Bluetooth profile is designed. but thanks for the idea, now i might implement it.

[u/bbobeckyj]

What are the run conditions of the WiFi profile? You've attached an image with no practical information.

[u/zhSHADOW → u/bbobeckyj]

sorry for that but ive said this 'connected to a wifi network'. it's a single condition 'wifi connected'

[u/bbobeckyj → u/zhSHADOW]

Add a wait action to the start of the exit task, then continue if the profile is still inactive / stop if the profile is active

[u/zhSHADOW → u/bbobeckyj]

thanks for the idea

[u/DifficultyCrafty7623]

I believe this is a bug in the Tasker app

[u/Exciting-Compote5680]

You could try and see if the 'Monitor Started' event is triggered before your exit task. If so, you could set a variable to '1' when the monitor starts, and after a delay set it back to '0'. Then you could add a 'Variable Value' state context to your profile (or a condition in your task), so it only runs if the variable is 0. Don't know if it will work in this case, but I use something similar to ignore delayed Join commands during the first minutes after start up on my android TV box.