There is no limit to how long a Task can take to run. We have reports of users running a successful task across multiple days. Now, one thing that can limit the execution time is the agent where the task is running. If for some reason the team managing your agents need to restart them, the task will stop. Another common source of interruption is the timeout of the target of the task. For instance: databases usually have a timeout for SQL queries of a few hours, this can cause you task to fail, but isn't related to Runops.
My tasks are stuck with status
This means that the agent isn't picking up executions. Reach out to your company's DevOps team and tell them to check the agent. It could be a missing update or network problem. If you don't know how to reach your DevOps team, let us know and we will help.
Your own user is missing the group from the Target. You can either add the newly created group to your own user, ot add one of the groups from your use to the Target. The
admin group behaves like all other groups, so you need the
admin group in a Target to see it if you are an admin.
You can update all properties of a Target but the name, even if they are deactivated. When you add the wrong configurations to a Target, instead of deactivating it and creating a new one, update the properties of the Target with the name you want. Ask our team if you want to restore a deactivated Target in your account.
The best way to create a Template is to start with a Task. Use a Target without reviews to you can reduce the time it takes to see changes you make to your script. Ideally use the REPL in the CLI to make running your script similar to running it locally. When you get what you need running as a Task, add the variables and start testing it as a Template. One useful test for the variables is to print them to stdout so you can see them in the logs.