A Job's source determines whether it runs only on demand or also follows branch advances. A plain ref such as master, refs/tags/v1, or a full SHA is manual-only. trigger:master follows exact advances of master; the current supported trigger branch is master. A manual Run without an override uses the current head of that configured branch, while rp job run --source <ref> overrides one Run and never edits the Job.
Enable and disable deliberately
Use rp job update <job-number> --source trigger:master to enable automatic Runs for that branch, or rp job update <job-number> --source master to disable them. Changing a source to the plain branch does not cancel Runs already accepted for earlier branch advances. Inspect the Job's trigger history and Run list for dispatch and delivery failures; cancel a created Run through Run controls when necessary. Each automatic Run records the exact source and its provenance. A successful task merge may report that delivery is pending while the Run dispatch recovers; do not repeat the merge to force a build.
See build with a Job, Job inputs and list Runs. Job triggers are not App deployment triggers or Release publication.