How's your plugin runtime experience?

[tanutanu]

Hi guys,

I'm annoyed for a year or more when I call a plugin more than two times a macro run.
The first statement is ok, but the followings tend to have exceeded the reasonable running time, more than 5 seconds typically. Some of these are longer than 10 seconds, but become shorter suddenly, less than a second sometimes.
Most of my logics processes through Termux:Tasker plugin, so not heavy load in most cases, almost same as shell script actions.

For waiting the unconstant returns, I often use Wait until action, however it is just waiting as long as it can resume, still waiting after the plugin timeout. So, my macro is suspended forever, never going on and just waiting missing return values, unless I turn on/off MD and start over, or resume rewriting a variable manually to fill the conditions.

I would like to hear you guy's experiences while using a plugin in your macro.
Does it work without any problems? Do you got a same running time as Tasker? Is it constant? How are you doing when you have a performance issue?
Please tell me your opinion and experience with the specific plugin name

Last night(about 3pm now for me), I wrote a macro to show me some runtime info on a overlay window with TouchTask. Yes, it works, but the runtime performance is very bad even though just calling one time a execution.
I added some wait actions to avoid too much stacked actions. It might be just a ""charm" but I feel it effective and don't know any other reasonable way to solve the problem logically

 

[Jacob L]

If you follow steps at dontkillmyapp.com for all of the plugins and MacroDroid that might help.

In some vases in echo, people have better experience using single quotes rather than doubles.

You don't need the invoked constraint twice.

I have some issues with Foldersync pro but that's the app itself not the plugin side.

 

[tanutanu]

If you follow steps at dontkillmyapp.com for all of the plugins and MacroDroid that might help.

In some vases in echo, people have better experience using single quotes rather than doubles.

Thank However, the settings not only MD but plugins are ok. I don't ask such a basic trouble shooting
TouchTask can be in both foreground and background as its option and it doesn't the matter for my issue.

You don't need the invoked constraint twice.

Yeah, I know that, but leave it at this moment. That's definitely neither the reason of the problem or what I want to talk about. I don't ask you debugging my macro as well

I have some issues with Foldersync pro but that's the app itself not the plugin side.

That's related what I want to talk about, but you told not the plugin side
Excuse me, so what's your plugin story?

 

[Jacob L]

Thank However, the settings not only MD but plugins are ok. I don't ask such a basic trouble shooting
TouchTask can be in both foreground and background as its option and it doesn't the matter for my issue.


Yeah, I know that, but leave it at this moment. That's definitely neither the reason of the problem or what I want to talk about. I don't ask you debugging my macro as well

That's related what I want to talk about, but you told not the plugin side
Excuse me, so what's your plugin story?

It is always best to start off basic as even the best people in the world make mistakes. You did in fact technically ask for your macro to be debugged, because it may have been the macro causing issues so it is best to rule that out.

As for my plugin, it seems to have issues with FTP transfers for my webpage. It isn't clear why but it is with the app not the plugin because the plugin is called like it is meant to. It is more likely a server issue

 

[tanutanu]

It is always best to start off basic as even the best people in the world make mistakes. You did in fact technically ask for your macro to be debugged, because it may have been the macro causing issues so it is best to rule that out.

As for my plugin, it seems to have issues with FTP transfers for my webpage. It isn't clear why but it is with the app not the plugin because the plugin is called like it is meant to. It is more likely a server issue

I had experienced in various environments. It doesn't depend on each state, such as these OS versions/device manufacturers/macro s/plugins unfortunately. I always suspect my macro bug or misconfiguration first of all.
The disconstruction had done again and again. First I thought it happened in plugins developed by a author due to his SDK/library/development environments or so, but seemed to be different

Anyway, I meant I want to hear another plugin story, not the breakdown of your issue on the server side Please tell me if you have

 

[FrameXX]

I often use Wait until action

I always try to avoid using this action if possible. It likes to violate if constraints if you have some in your macro. I don't trust it.

 

[tanutanu]

I always try to avoid using this action if possible. It likes to violate if constraints if you have some in your macro. I don't trust it.

Is it Wait Until action problem or caused by a plugin? seens to be working well with MD variable Change condition for me.
I had not used it for a while but noticed it suitable especially when a macro prompt a user choice via UITask.

 

[420]

Is it Wait Until action problem or caused by a plugin? seens to be working well with MD variable Change condition for me.
I had not used it for a while but noticed it suitable especially when a macro prompt a user choice via UITask.

I had problems with UItask in combination with the wait untill action aswell, my solution has been to add the variable change as a seperate trigger to the macro and then i just use another if (trigger fired) clause and put the following actions in there. So the wait untill action is no longer needed/used and i have not had any problems since then.

 

[tanutanu]

I had problems with UItask in combination with the wait untill action aswell, my solution has been to add the variable change as a seperate trigger to the macro and then i just use another if (trigger fired) clause and put the following actions in there. So the wait untill action is no longer needed/used and i have not had any problems since then.

Interesting.
I use the same trick as a backup when an unknown stacking happens while waiting the return value from Termux.
Probably the plugin side process delayed too long, or timed out and no longer responded. Thanks for the information