Credentials, nodes and schedules
Can anyone read a secret I stored in a credential?
No one can read it in the console. A secret is written once and never shown on screen again, not even to you: only the tasks the credential reaches receive it. When you open the credential, its secret fields stay empty and say Leave blank to keep the stored value. To change a secret, type the new value into the same credential. Never paste a secret into a task's description, a project's commands or its agent instructions: anyone who can view those can read it.
See How credentials work and Replace or delete a credential.
What's the difference between a credential and a model account?
A credential connects your tasks to the services their work touches, such as Jira, Slack, GitHub or AWS. A model account is what a runner signs in as to reach the AI model itself. Credentials live under Directory, then Credentials; model accounts under Directory, then Model Accounts.
See How credentials work and Model accounts.
Does draining a node stop the tasks running on it?
No. Drain stops the node taking new tasks and lets the ones it's running finish; then the node disables itself. Disable stops new tasks at once, and running tasks carry on too. Only Delete ends what's running: it removes the node and every worktree on it, and can't be undone.
See Drain or disable a node and How nodes work.
Why can't I see Schedule under Automation?
Schedule is shown only to Owners and Admins of your organization. Everyone else sees only the Playbooks tab under Automation. Ask an admin to create the schedule for you, or to grant you the role.
See How schedules work and How team and access work.
Will a task a schedule filed stop to ask me questions?
That depends on the schedule's Full auto setting. On, the runner never asks you anything and fails instead when it needs a person. Off, it stops, asks and waits for your answer, like any task you started yourself.