# Tasker API Timeout Frequently **URL:** \ **Category:** Support\ **Tags:** kodi\ **Created:** [May 20, 2025, 12:40am UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160 "2025-05-20T00:40:53Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wingman1487](https://community.yatse.tv/letter_avatar_proxy/v4/letter/w/8e7dd6/32.png) [@wingman1487](https://community.yatse.tv/u/wingman1487)\ **Post date:** [May 20, 2025, 12:40am UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160/1 "2025-05-20T00:40:53Z")
**Issue description** : I have several Tasker commands that I use to change my Media Center and kickoff library syncs depending on some conditions. The commands are kicked off successfully in Tasker, however over the last few months I’ve been getting a lot of timeout errors from Tasker waiting on a response back from Yatse, then Yatse crashes and does not complete the action. Digging into the debugging logs it looks like it’s got something to do with the Yatse services not getting to the foreground and timing out. I’ve gone ahead and tried disabling any battery optimization on Yatse to see if that would help however no joy. The Tasker commands work fine when testing from Tasker, but the Phone Screen is on so I’m wondering if it’s got something to do with the Phone sleeping. I have the full log, however here is the lines that I see where Yatse crashes after the Tasker call and then re-initializes. > 2025-04-16 14:10:38.481 Error/Crash: Unhandled crash in Thread[main,5,main] > android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{3defa5c u0 org.leetzone.android.yatsewidgetfree/com.joaomgcd.taskerpluginlibrary.action.IntentServiceAction c:net.dinglisch.android.taskerm} > at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2349) > at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2317) > at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0) > at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2691) > at android.os.Handler.dispatchMessage(Handler.java:109) > at android.os.Looper.loopOnce(Looper.java:232) > at android.os.Looper.loop(Looper.java:317) > at android.app.ActivityThread.main(ActivityThread.java:8934) > at java.lang.reflect.Method.invoke(Native Method) > at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591) > at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911) > 2025-04-16 14:10:41.228 Verbose/MainInstance: initialize: komodo/komodo/35/15/Pixel 9 Pro XL/google/0/true/false/68/126/201 **Logs** : (Join files do not paste the content of the files here !) [debug-20250416\_142909.zip](https://community.yatse.tv/uploads/short-url/8R9ZzFv5qPoEiyG7VCe1NCtl1z3.zip) (3.2 MB) **Screenshots** : ![Screenshot_20250414-165833](https://community.yatse.tv/uploads/default/original/2X/b/b2daaad78593eeba72dcfc24a2262a442a833188.png) **Additional information** : ---
**Author:** ![Tolriq](https://community.yatse.tv/user_avatar/community.yatse.tv/tolriq/32/12_2.png) [@Tolriq](https://community.yatse.tv/u/Tolriq)\ **Post date:** [May 20, 2025, 7:38am UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160/2 "2025-05-20T07:38:56Z")
You probably need to update your Tasker version, this is internal to the tasker plugin and tasker now binds to the service and no more tries to just start it. ---
**Author:** ![wingman1487](https://community.yatse.tv/letter_avatar_proxy/v4/letter/w/8e7dd6/32.png) [@wingman1487](https://community.yatse.tv/u/wingman1487)\ **Post date:** [May 20, 2025, 2:05pm UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160/3 "2025-05-20T14:05:15Z")
I’m on Tasker v6.4.15 that was release Feb 28th 2025. They don’t have any newer version that I’m aware of from the Play Store unless I went with one of their Nightly builds (looks like they have a 6.4.16 via a direct APK download). I can give that direct download a shot and see if it does any better, if not your suggestion is it’s a Tasker issues and not a Yatse issue? Is Tasker causing Yatse to crash when it calls it? ---
**Author:** ![Tolriq](https://community.yatse.tv/user_avatar/community.yatse.tv/tolriq/32/12_2.png) [@Tolriq](https://community.yatse.tv/u/Tolriq)\ **Post date:** [May 20, 2025, 2:36pm UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160/4 "2025-05-20T14:36:09Z")
Yes the service that fails is : `com.joaomgcd.taskerpluginlibrary.action.IntentService` That service is from the tasker Library and it’s not supposed to try to start it foreground at all ---
**Author:** ![wingman1487](https://community.yatse.tv/letter_avatar_proxy/v4/letter/w/8e7dd6/32.png) [@wingman1487](https://community.yatse.tv/u/wingman1487)\ **Post date:** [May 20, 2025, 3:14pm UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160/5 "2025-05-20T15:14:23Z")
Ok, let me give the new version a try and if it’s still kicking back these timeouts I’ll open something up with the Tasker folks. Thanks for looking into it and your insight, love the app and all the work that has been done with it to make it what it is today! ---
**Author:** ![wingman1487](https://community.yatse.tv/letter_avatar_proxy/v4/letter/w/8e7dd6/32.png) [@wingman1487](https://community.yatse.tv/u/wingman1487)\ **Post date:** [November 14, 2025, 3:42pm UTC](https://community.yatse.tv/t/tasker-api-timeout-frequently/5160/6 "2025-11-14T15:42:41Z")
Sadly I haven’t been able to get anywhere with this. Tasker points one way, Yatse points the other. Is there maybe a workaround for this that I could try, or maybe a way to make a custom API call from Tasker without using the Yatse integration?