#Can't override schedule

1 messages · Page 1 of 1 (latest)

visual spruce
#

Previously running this command would run outside the schedule not working in kometa.

Any ideas to look into

versed pulsarBOT
#

Welcome @visual spruce!

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

#

You can press the "Close Post" button above or type /close at any time to close this post.

daring sparrow
#

What env vars do you have setup?

visual spruce
daring sparrow
#

KOMETA_RUN: False

#

that means it will not run immediately

#

I believe Environment Variables take priority over Run Commands

#

the wiki states:
However, if you encounter a race condition where an attribute has been set both via an environmental variable and a shell command, the environmental variable will be given priority.

molten meadow
#

Yep, KOMETA_RUN is winning.

visual spruce
#

Hmmm anyway to overcome that. When this was pmm i had it set as a schedule on the ENV VAR and ran a docker exec command every 4 hours for overlays only

#

I tried the docker run, but it just keeps making a bunch of stopped containers after the script is done executing

molten meadow
#

remove KOMETA_RUN

#

docker run will leave the containers around unless you add the --rm flag.

visual spruce
#

K

#

Thank you