# Cron/manual tasks should never be started

**URL:** <https://forums.suse.com/t/cron-manual-tasks-should-never-be-started/4210>\
**Category:** Rancher 1.x\
**Created:** [October 6, 2016, 7:02pm UTC](https://forums.suse.com/t/cron-manual-tasks-should-never-be-started/4210 "2016-10-06T19:02:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pschrammel](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pschrammel/32/1753_2.png) [@pschrammel](https://forums.suse.com/u/pschrammel)\
**Post date:** [October 6, 2016, 7:02pm UTC](https://forums.suse.com/t/cron-manual-tasks-should-never-be-started/4210/1 "2016-10-06T19:02:57Z")

</div>

Hi,

I have some manual tasks (setup) and cron tasks (managed by rancher-cron) which should never be started. I’ve set the start\_once=true label and even set scale:0 but on upgrade the services are still run (just once but even that’s too often).

Is there a solution to avoid this or how do people use rancher-cron or add service definitions in docker-compose which should not be run at deployment time.