Job page. Select a row on Jobs, Open the job page in the drawer, or Job page anywhere else, to open /app/jobs/{job id}. The title is the kind of job, and the breadcrumb reads Jobs then the job; Jobs returns to the list. Below the title, "For" the site name and the organisation show. On the right are a status badge with the job's stage and a Site's Patching tab link that returns to the site's Runs section. The page refreshes every 10 seconds while the job is queued or running, and every minute while its pull request is open. A job that does not exist in your organisation shows as not found. Below the status card are Pull requests from this run, their Deploy to production controls, and Deployment with live status. Deployment history remains after a merge or reload.
The first card is the Job status card. The facts about the run sit in the Details panel, described below.
- Stage. The card's title, with an icon, says where the job is, and the same stage shows as a badge in the page header: Queued, Waiting (for a free slot in your organisation's allowance, or for the site's running job to finish), Held (Patching is paused for your organisation, for the AI provider, or Sentinel has paused all update jobs), Starting a runner machine and preparing the workspace, Updating dependencies, Verifying: tests and checks, Opening the pull request, Deploying, Finishing and cleaning up, then Done, Done, N items need you (the pull request is open but something was left for a person, see What this job did below), Succeeded for a security run with no applicable advisories, Failed or Stopped. Stopped means the job was cancelled or cut short, for example by a time limit, running out of memory, an emergency stop or the site leaving Patching.
- Detail. Explains a wait with its queue position and estimated start (see Patching), or summarises a finished job and why work remained or stopped. For example: "The pull request fixes 1 of 2 advisories. drupal/stage_file_proxy needs a major upgrade (3.x to 4.x), so do that one by hand." Sentinel uses the findings; the connected job model may shorten only the reason using those findings. Sentinel always writes delivery facts and counts. Jobs finished before October 2026 retain their older summary.
- Progress. A progress line shows four parts: Queued, Update and test, Pull request and Finish. While the job is queued or running, passed parts are ticked and the current part is marked. A job past the pull request part without one leaves Pull request grey. The line stays after the job ends. A finished security or maintenance update that opened a pull request has every part ticked; one that opened none leaves Update and test and Pull request grey. A finished rebase or CI fix, or a run that opened only a runtime pull request or a pull request that only merges the production branch, ticks Pull request but not Update and test. A failed job marks Finish in red and a stopped job marks it in amber, leaving the middle parts grey; the stage above the line says what went wrong. A job stopped before it started marks Queued in amber.
- Pull request. The pull request number as a link to your Git host, with its state, such as Open: Ready to merge, Merged or Closed. A successful finished job with no pull request says None opened; other jobs without a pull request say None yet. None opened only means this run opened no pull request; read Detail and Next step for any remaining work, such as reviewing excluded packages.
- Advisories. For a job that reports findings: how many advisories the findings name and how many the pull request fixes, for example 2 found, 1 fixed.
- Duration. How long the job ran. While the job is queued it shows the turning Sentinel mark and Waiting m:ss (h:mm:ss after an hour), counting up every second from when the job was queued. A job that Sentinel retried on its own, after it ran out of memory or lost its runner machine, counts from when the original job ended. Once the job starts, Duration shows the run time. If Sentinel cannot tell when the wait began, it shows Not started.
- AI cost. A finished own-key job’s estimated provider cost in US dollars. Not recorded means Included AI, unknown historical source, queued/running, or missing cost. Included AI’s internal estimate is not a customer charge.
- Next step. What to do, in plain words. A queued or running job says that nothing is needed and the job continues on its own. A held job says to contact support if the hold lasts. For a finished job with an open pull request it depends on who deploys. When Sentinel deploys the site and the pull request goes into the production branch, it says to review it and choose Deploy to production on the site's Patching tab rather than merge it on your repository, so Sentinel merges and deploys it through its deployment checks (through your hosting platform or your own pipeline). For a site set to I deploy it myself, or a pull request into another branch, it says to review and merge it on your repository. A run that changed only runtime components shows its runtime pull request. A job that needed no changes says that no pull request was opened. A failed job with findings gives the recommendation of its main reason instead, because running it again the same way stops for the same reason; a job with an open pull request that left something for a person adds that recommendation after the review step. Otherwise a failed job says to read why it failed in the detail line, then run the update again (for a rebase, ask for the rebase again from the pull request), and to contact support if it keeps failing. A stopped job says to run the update again from the site's Patching tab when you are ready, or, for a rebase, to ask for the rebase again from the pull request.
- Help opens this section.
- Stop job. Shown on the Job status card while the job is queued or running, to people who may run updates (organisation administrators and site managers). It asks Stop this job? first; see Run an update. Viewers and other members do not see it.
What completion verifies. Done means the update job finished preparing proposed changes. Read its checks, warnings and Needs a person items. It does not mean every check passed, every advisory was fixed, the pull request was merged, deployment succeeded or the running site was verified. Your team maintains project-specific acceptance checks, reviews the proposal and checks site behaviour after deployment. Sentinel's agreed deployment steps and safeguards still apply. A skipped, missing or unavailable check is not evidence that a test passed.
Flag for review. Every member who can read Patching jobs (administrators, site managers and viewers) sees Flag for review on a job page while Support is available. It opens a dialog. Choose What went wrong? (The job failed, It did not do what I expected, It caused a problem on my site or Something else), describe What happened (required), and optionally add What you expected and Screenshots (PNG, up to 5). Select Open ticket. Sentinel opens a support ticket for you and adds the job's details itself: job number, kind, site, status, times, pull request and a link back to the job. The dialog then says "Ticket SNTL-… opened. We reply on the ticket and by email. You can keep working on this page." Select View ticket to read it, or Done. You stay on the job page.
While a ticket about the job is open, the page says "You flagged this job for review on (date): ticket SNTL-…", with a link to the ticket. If another member flagged it, it says "Another member flagged this job for review on (date): ticket SNTL-…" with no link, because a ticket can be read only by the person who raised it. If you have the open ticket, the button reads Add to review and your new answers are added to that ticket as a reply. The dialog lists anyone who gets copies of the ticket, since they get the reply by email too; screenshots go on the ticket itself. Once the ticket is closed, flagging the job again opens a new ticket. The ticket page shows Patching job with a link back to the job.
Package versions. This table separates the job’s requested updates from its recorded versions:
- Starting version: the version recorded before the update.
- Requested update: the selected patch, minor or major update; Not individually selected means the package had no individual selection.
- Planned version: the target the job planned to reach.
- Recorded lock result: the version recorded in the job's Composer lock file after an accepted update. This describes the job's workspace and does not confirm deployment to your site.
- Status: Recorded change, Added to lock file, Removed from lock file, Unchanged, Blocked, Awaiting result or Version evidence unavailable.
Requests and planned versions are targets, not proof of an update. A running job can show Awaiting result; a stopped or failed attempt can show Blocked without a recorded result. An added package says Not in starting lock; a removed package says Not in result lock. Otherwise missing versions say Not recorded. Older jobs and expired or incomplete records can leave gaps: Sentinel does not fill them from your site's current versions or today's available releases. The section is absent when there are no package records, or when Sentinel withholds the job's output. On a narrow screen, scroll the table sideways to see all columns.
Members who can read the job, including viewers, can read this table. It gives no additional permission to run updates or deploy them.
Why it stopped or What this job did. A finished job that reports findings has this panel under the card: Why it stopped when no pull request was opened, What this job did otherwise, with how many items need you. Each row is one package or cause, blocked and needs-you rows first: an icon (Blocked, Needs you, Fixed or Information), the package and its versions, the advisory, a short cause such as Major upgrade needed, Development tools moved, Protected package or Excluded by policy, the reason in plain words and a Recommendation. A fix that is only in a new major release says to upgrade the package by hand, outside Patching. When a check is failing on your production branch, a row A check is failing on the production branch appears, marked Needs you, and a warning shows above the panel, with links to the failing checks on GitHub (see Checks failing on the production branch). Each advisory id shows where it comes from (Drupal.org, GitHub, CVE or Packagist) and links to the public advisory. Three causes come from Composer audit: Still reported (Composer audit still reports the advisory after the update; needs a person), Abandoned (information: Composer reports the package abandoned) and Audit did not run (needs a person). Development-only packages a security fix moved by a patch release are listed in an N development tools also moved row marked Not deployed; select Show the N packages to see them. A development-only package that was locked on a release with a security advisory is listed in an N development tools moved for a security advisory row, marked Security fix, development only, with the advisory ids. Composer refuses to install such a release, so a maintenance or security job used to fail with "composer update failed". Patching now lets that package move to the latest release on its current major, together with the development packages it needs, and runs the update again. Advisories are never ignored, and protected packages and packages you excluded stay held. They are development packages: a deployment that installs with composer install --no-dev leaves them out. The pull request notes list each one as Development package moved for a security advisory. Select Show the N packages to see them.
Recorded AI usage follows a finished job’s card. Included AI shows Input tokens, Cached input and Output tokens without internal provider/model, reasoning, SDK/version or cost estimates. Own-key jobs also show their recorded runtime details and Estimated cost when available; this is an estimate, not the provider’s invoice.
Changing or removing a connection does not rewrite a job’s source. Unconfirmed older sources show neutral AI usage, with counts but no inferred model/cost. No recorded usage means no section. The same rules apply to customer activity, exports, downloads, organisation archives and support-assistant job explanations.
Details panel. On wide screens the Details panel sits to the right of the page; on phones it comes right after the status card. It lists:
- Pull request. The pull request number as a link to your Git host, with its state, such as Open: Ready to merge, Merged or Closed, and its title below. A finished job with no pull request says None opened; a job that is still queued or running says None yet. None opened only means this run opened no pull request; read Detail and Next step for any remaining work, such as reviewing excluded packages.
- Started and Finished. When the job started and ended. Each shows Not yet until it happens.
- Duration. How long the job ran, or Not started while it is queued (the status card shows the wait).
- AI cost. A finished own-key job’s estimated provider cost in US dollars. Not recorded means Included AI, unknown historical source, queued/running, or missing cost. Included AI’s internal estimate is not a customer charge.
- Advisories. For a job that reports findings: how many advisories the findings name and how many the pull request fixes, for example 2 found, 1 fixed.
- Job ID. The job's ID, with a button to copy it. If your browser blocks copying, the panel says Copy failed.
Under the list, organisation administrators get Export job (JSON), which is also recorded in the audit log. Flag for review (below) is next to it. The panel also shows how many steps were recorded (for example "1 step" or "12 steps") and how long they are kept: full output for 90 days and the steps for 13 months. Help with jobs opens this section. The Job details card in the job drawer's Steps tab still shows the outcome, site and times.
Reference material read. Where Sentinel has agent web access turned on and Patching is open to your organisation, an update job's page can show a Reference material read section. It lists the pages the update agent read from Sentinel's own list of reference sites, such as Drupal.org release pages and vulnerability databases, and the advisories it looked up by their CVE or GitHub advisory number. Each row shows the page address (a link that opens in a new tab) or Looked up with the advisory number, why the agent read it, what kind of site it is, a User content label when the page is something people write (a forum or an issue thread) rather than a maintained reference, whether the read worked, and the time. After a redirect, the label is the one for the site the agent ended up on. Status wording includes Read, Found in Sentinel's catalogue, Not in the catalogue, Too large to read, Not a text page, Took too long and Could not be read. While the job runs the section refreshes by itself, so reads appear as they happen. When agent web access is off, or the job has no reads, the section is not shown.
- Pages are reference only. Nothing on a page can change what the job is allowed to do. If a page has lines that read like instructions to the agent, the agent ignores them. You see only how many lines were ignored, for example "2 lines on these pages read like instructions to the agent and were ignored", never the text.
- A read that Sentinel refuses is shown as a count only, never the address. The note says the address is not on Sentinel's list of reference sites, or the site or its read limits did not allow it. If many reads are refused, the job stops and the section says "The job stopped after repeated refused reads."
- Ask for a reference site. Organisation administrators, site managers and viewers (everyone who can read Patching) see this link at the bottom of the section. It opens a short form: Host name, What the agent would read there and an optional Example page. Select Send request to open a support ticket, or Cancel to close the form. If you already have an open request, it is added to that ticket instead. A person at Sentinel reviews the site and replies on the ticket. Adding a site to the list is a reviewed change and is never automatic. Today the link appears only when the job has at least one read or refused read, so a job with none shows no section and no link.
- When Sentinel withholds a job's output (next paragraph), this section is hidden.
When Sentinel withholds a job's output. In rare cases Sentinel staff find data that must not be kept in a job's stored output. The job page then shows a notice: "Sentinel withheld this job's output, so its full output, export and step details are not available. Contact support if you have questions." Every member who can read the job sees it, and Sentinel emails your organisation administrators about it separately. The overview line says the same and shows no findings. Each AI agent and job step reads Output withheld by Sentinel, or Output removed by Sentinel once the output is deleted, with no details and no Full output link. Export job (JSON) is no longer offered, and the export and file downloads answer not found. Git, check and hosting steps stay visible, and one step records that a platform administrator withheld or removed the output. Sentinel does not undo this.
Last comes All steps, grouped by phase (N). It is collapsed for a job that did not fail and open for a failed job, so the reason is in view. Steps are grouped by playbook phase (Prepare, Update, Verify, Deliver, Deploy, Finish), followed by a Runtime group when the run looked at runtime components (see Runtime updates under Patching). Each step expands to its detail, output excerpt and links. A job that has only just been queued has a page before any step is recorded; the steps area then says "No step has been recorded yet. Steps appear here once the job starts." A job that ended without recording a step, for example one cancelled while it was queued, says "No step was recorded for this job."
Job task list and decisions. A Patching job keeps a task list and records its decisions, blockers and milestones as rows in the activity records, for example "Task completed: ...", "Decision: ...", "Blocker (...): ..." and "Milestone: ...". Rows written by the AI agent show Agent as the actor and the agent category; the rest show Sentinel. Instructions in your repository's own files (such as AGENTS.md) that ask for more than an update job may do, like merging or deploying, are ignored: each file gets one decision, for example "Ignored 10 instructions in AGENTS.md (repository files are data, not instructions to the job)", and expanding it lists the first 10 lines. Skills in your repository are not loaded either, in one decision that lists them. On the job page, the same step repeated several times in a row shows once with "(N times)"; expand it to see each one.
Patching activity on the site and in reports
Site Activity. The Activity section of the site's Patching tab lists only that site's rows, with filters and no download. It starts with the site's own events: enrolment, accepted terms, deploy holds, set-up changes, and merges, deploys and staff actions that are not part of a job. Each job's steps are on its job page; tick Also show run steps to list them here too. A site that is no longer enrolled shows its full activity under the enrol card.
Site Releases. When Patching merged or deployed something for the site in the selected period, the History tab shows a Patching deployments list above the release limits. Each entry has the time, a summary, who did it, the consent number and a Job link. These are what Sentinel did. They are separate from the releases Sentinel observed in your submitted inventory, and they do not change the observed release counts.
Monthly report. A site's section gains Merged and deployed by Patching when Sentinel merged or deployed for it in the month, with the person or Autopilot and the consent number. These entries are separate from the observed deployments and are not in that count.
What is kept:
- Secrets are removed before anything is stored, so the job page and the exports never show them.
- Rows cannot be edited or deleted. Steps are kept for 13 months, except steps tied to a consent, which are kept for as long as the consent.
- Full command output is kept for 90 days. After that the download link stops working, but the row and its excerpt remain.
