Sentinel records each step that Patching takes for your sites. Members of the organisation can read these pages. Organisation administrators can also download the activity records from the Every step view. A platform administrator who is not a member of your organisation cannot open them. Nothing here is visible until Patching is enabled for your organisation.
Jobs page. Open Jobs in the sidebar (/app/jobs; on a phone, the Jobs tab). It lists every update job of the selected organisation: security, maintenance and rebase jobs. The list shows 25 jobs a page.
- State chips sit above the list, each with a count: Needs you (a finished job whose pull request, or paired runtime pull request, is still open; an Autopilot run that is moving on by itself, waiting for checks or its window, deploying or verifying, is not counted), Running, Queued, Done (every other finished or stopped job), Failed and All. The counts follow the Site, Kind and Period filters.
- Period has Any time, Last 7 days, Last 30 days and Last 90 days. There is no Status filter any more; use the chips. Select Clear filters to start again.
- Columns are Site (with how the job started: Run by a person (from the site, a finding or a Dependabot alert), Autopilot, Scheduled, CI fix by Sentinel, Retried by Sentinel or Started by Sentinel), Kind, State, Pull request (a link that opens your Git host in a new tab, with the pull request's state), Started and Took.
- In All, the order is set before the list is split into pages. Jobs that need you come first. Running and queued jobs follow under Running and queued. All other jobs come last under Earlier jobs.
- The Failed chip adds a Why column and one repair button per row. Fix connection (a clone or workspace failure) opens Settings, Patching. Raise cap (an AI budget or cap stop) opens Settings, Patching, AI keys. Rebase (a failed rebase or CI fix job) opens the site's Patching tab. Retry (a failed security update that a person started from the site) queues the same update again with the site's own checks. Retry is for people who may run updates. Other members see Open site instead. A failed maintenance update also shows Open site, because it may have asked for PHP or other runtime release lines. So does a job that Autopilot, a schedule, a finding or a Dependabot alert started, because it chose what to update in its own way. Run these again from the site's Patching tab.
- While a job is queued or running, the list refreshes by itself every 10 seconds, and every minute while a pull request in the list is still open.
- Before any job has run, the page says "No update job has run yet" and links to Sites, where you can enrol a site and run an update.
Run security update. Organisation administrators and site managers (people who may run updates) see Run security update in the header of Jobs. It opens a dialog. Pick an enrolled site and confirm. Sentinel queues a security update through that site's own run request, so the site's readiness, plan and consent checks still apply. Nothing deploys from this button. Viewers do not see it.
Every step. Select Every step above the page (or open /app/jobs?view=activity). It lists every recorded step across your sites, newest first: job steps, the AI agent's tool calls, Git host events such as a pull request being merged, hosting platform calls and deployments, and gate decisions, consents and notifications that belong to no job. Each row shows the time, a category badge, a summary, the site, who or what did it, and a success or failed badge where the step finished. The actor is a person by name, Autopilot, Sentinel, Agent or Git host. Select a row to expand it. It shows the detail, an excerpt of the output, links (the pull request, the platform log, a download of the full output and the Job page) and the consent record number when the step ran under a consent.
- Filter by Category, Actor, and From and To dates, and move between pages. Select Clear filters to start again. A filter with no matches shows an empty list, not an error. The Jobs Period filter does not apply here.
- Before any job has run, the page says that activity appears once the first update job runs.
- Download activity. Organisation administrators (people who can configure Patching) see this button in the Every step view. It downloads a CSV for the dates in that view's filters, or the last 30 days when none are set, and at most 400 days at a time. Every download is recorded in the audit log. Other members do not see the button.
Job drawer. Select Details to open the job in a drawer on the right. Select anywhere else on a row, or its site name, to open the job's page instead. The chip, filters and page you chose stay in the address, so the browser's Back button returns to the same list. On a phone the drawer fills the screen. Its tabs are Summary, Steps, Pull request and Deployment. Deployment shows the deployments of this job or of its pull request. The address gains ?job= and the job's number, so you can link to the open drawer. Press Escape or select Close to close it. The drawer links to Open the job page and to the site's Patching tab. While the job is queued or running, the Summary tab shows Stop job to people who may run updates (see Run an update).
Patching on Home. The Patching section of Home shows four counts. Sites enrolled, Ready to update and On Autopilot are the current figures. Deployed this month counts the deployments that a site confirmed since the start of the organisation's month, in its time zone. These are deployments Sentinel made. Its note reads "confirmed by the site", then how many pull requests were merged and how many jobs finished this month. A site that deploys itself shows only in the merged count. One usage card holds your plan usage and the Included AI line. It shows only to people who can read Patching, while Patching is on for your organisation. With no site enrolled it says "No site is enrolled in Patching yet. Enrol a site from Sites". Waiting on you (pull requests ready to merge, paused Autopilot, failed checks, approvals and drift holds) and Recent activity are in their own parts of Home, and Recent jobs are on Jobs.
Starting a job. Run security update and Run maintenance update (see Run an update under Patching) open the new job's page straight away, so you can watch it from the moment it is queued. In the site's Run an update panel an active job shows Open the job page, and the Past runs table has a Job page link on each row. Past runs lists every run of the site, newest first: Run, Requested, Took, Status, Pull requests, Outcome and Job page. The All, Security, Maintenance and Needs attention (failed or stopped runs) buttons narrow the list. It shows five runs at first; Show all N jobs shows the rest.
