![]() The reason I put that there is because it doesn't make sense to wait for the result of an asynchronous task halting the task and waiting for the results of the script is what "synchronous" means in this case.īasically, having no timeout on a Tasker action makes it asynchronous, and in termux-tasker's case that means it won't ever kill the resulting process (Because it doesn't need to, since it's not holding up the task)-but it also means you can't use the exit status or output in subsequent actions since you will probably run them before your script can finish. I don't know why they think the hostSupportsSynchronousExecution flags requires a timeout, maybe that's some Tasker limitation, the plug-in API is so poorly documented. ![]() (After which, you have the ability to override it in Tasker itself-but if you can't override it in Automate, then perhaps you have the ability to at least change that extra before it gets there) This post was made too long ago for me to reply, and I'm not really affiliated with Tasker or anyone else that can change how this all works, but the suggested timeout from the plugin should be in the .extras.REQUESTED_TIMEOUT extra in the intent sent to Tasker after configuration. The reason for a 10 second default was because most actions are pretty quick-and if something took that long, it was just less annoying to let someone set that time to a bigger number rather than force someone to wait longer if they accidentally did something that would never stop. Hihi! I'm the one who put that default there, and while I'm not sure how to set it from Automate, there is indeed an option for setting the timeouts in Tasker~ (10 seconds is just the default value the plugin suggests initially-so don't worry, it's not a hardcoded limit!) The ability to set, or remove the timeout If the Termux command completes in less than 10 seconds it is fine, but if not it fails.Ġ1-21 11:30:13.290 I Flow beginning 01-21 11:30:13.291 I Plug-in action 01-21 11:30:13.368 D PlugInSetting ACTION_FIRE_SETTING: resultCode=3 01-21 11:30:13.369 D Starting 10000 ms timeout, as requested 01-21 11:30:23.388 F : Plug-in didn't respond within requested timeout 01-21 11:30:23.390 I Stopped by failureĬreate a new Automate flow, add a termux task that takes longer than 10 seconds to execute. I have an issue using the Termux Tasker plugin with Automate around timeouts.
0 Comments
Leave a Reply. |