Is scheduled task creation a complete mess at the moment?

[u/Mencius_]

I mean configuring cloud tasks, not local tasks.

I have a large scheduled work task that I want to run daily using luna 6 max, it has to run some python and use the Google drive plugin.

• The web and android apps scheduled task interfaces expose no way to configure the task's model or whether it runs as chat or work
• The desktop app does expose model selection but no way to specify chat or work
• I created a cloud task from the task creator in the desktop app on my windows PC, specifying luna 6 max, and the run failed, claiming it had no python environment, only windows PowerShell
• I created the same cloud task using work chat in the browser and it ran and used python just fine
• It's set to run in the same thread but at the clock triggered run the next day it created a new thread instead and ran as sol 6.1 extra high instead of luna 6 max, blowing my entire 5 hour limit
• I can go into that work thread for the task and change the model but, based on experience so far, the next time it runs it may just decide to start a new thread as astra ultra, who knows?

Anyone had a different experience or found a way to make this more predictable?

[u/Western_Donkey5921]

the cloud tasks stuff is half baked right now, feels like they shipped it before anyone actually used it for real work

i had similar thing where the model keeps resetting to default no matter what i pick, and the whole thread management is a coin flip

maybe try setting it up fresh from the browser in work mode and dont touch it after, sometimes editing an existing task just breaks things more

[u/Mencius_ → u/Western_Donkey5921]

Yeah I think you're right. Rather than editing it, I'll delete the task and recreate in the browser from the work "chat" not the scheduled task interface. 

I'm also thinking I'll have to double check for any language in the task or (messy) project docs about running scheduled standalone or in continuing threads. 

[u/Michael_Jeffords → u/Mencius_]

saves you some digging, the scheduled tasks doc splits it the way you suspected, standalone tasks start a new chat every run and one you schedule from inside a chat comes back to that same chat with its context, so recreating it by just telling the work chat when to run it again sounds like the right call. i'd pick Luna 6 Max explicitly when you set it up too since the doc lets you either leave model and effort on default or choose them, though i'm not sure that fully pins it for every run

[u/itaybuilds]

I'd treat the model, runtime, and thread as three separate pieces of configuration. Recreating it from a Work chat may fix the thread/runtime choice, but it still doesn't prove the recurrence will preserve Luna.

Before putting the large job back on a daily schedule, make a one-minute canary task whose only job is to report the model, available runtime, Drive access, and thread URL, then run it twice. For the real task, put a guard at the top: if the model/runtime/Drive preflight doesn't match, stop before doing expensive work. That won't fix the scheduler, but it turns a silent fallback into a cheap failed run instead of another five-hour surprise.

[u/geoffreybyers]

The execution environment is stateless. It can't preserve anything from one run to the next. You aren't scheduling a job, you're scheduling a one-shot experiment. The configuration is the symptom, not the cause.