Skip to content

Commit 1bc4f60

Browse files
committed
Move whitehall scheduled publishing docs from alerts
There's no longer an alert for this, but the docs still seem useful. Moving them to the Publishing section so they're not lost, and making some slight changes to wording / updating a link.
1 parent 64785c7 commit 1bc4f60

File tree

4 files changed

+10
-9
lines changed

4 files changed

+10
-9
lines changed

config/tech-docs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -149,6 +149,7 @@ redirects:
149149
/manual/alerts/elasticsearch-cluster-health.html: /manual/elasticsearch-cluster-health.html
150150
/manual/alerts/email-alerts.html: /manual/alerts/email-alerts-travel-medical.html
151151
/manual/alerts/publisher-unprocessed-fact-check-emails.html: /manual/publisher-unprocessed-fact-check-emails.html
152+
/manual/alerts/whitehall-scheduled-publishing.html: /manual/whitehall-scheduled-publishing.html
152153
/manual/archiving-and-redirecting-content.html: /manual/redirect-routes.html
153154
/manual/bouncer.html: /manual/transition-architecture.html
154155
/manual/bulk-email.html: /apps/email-alert-api/bulk-email.html

source/manual/help-with-publishing-content.html.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ necessary to help them to ensure it goes out as smoothly as possible.
3939
Safety Alerts go out correctly. Although an alert won't be triggered for other
4040
kinds of documents, the [guidance will still apply](alerts/email-alerts-travel-medical.html).
4141

42-
- If [a scheduled publication hasn't gone live](alerts/whitehall-scheduled-publishing.html),
42+
- If [a scheduled publication hasn't gone live](whitehall-scheduled-publishing.html),
4343
start here: [if documents aren't live after being published][live].
4444
If it looks as though the content was never published from
4545
Whitehall, there is a Rake task available which will publish overdue

source/manual/on-call.html.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,8 +60,8 @@ push notification). There are 2 ways that this might contact you:
6060
Any Icinga checks that use `govuk_urgent_priority` will cause PagerDuty to be notified:
6161

6262
- [Travel advice emails not going out](/manual/alerts/email-alerts-travel-medical.html)
63-
- [Overdue publications in Whitehall](/manual/alerts/whitehall-scheduled-publishing.html#overdue-publications-in-whitehall)
64-
- [Scheduled publications in Whitehall not queued](/manual/alerts/whitehall-scheduled-publishing.html#scheduled-publications-in-whitehall-not-queued)
63+
- [Overdue publications in Whitehall](/manual/whitehall-scheduled-publishing.html#overdue-publications-in-whitehall)
64+
- [Scheduled publications in Whitehall not queued](/manual/whitehall-scheduled-publishing.html#scheduled-publications-in-whitehall-not-queued)
6565
- [High nginx 5xx rate for www-origin on cache machines](/manual/alerts/high-nginx-5xx-rate.html)
6666

6767
You can get the most up to date list of these by searching the Puppet repo for [govuk_urgent_priority](https://github.com/alphagov/govuk-puppet/search?q=govuk_urgent_priority).

source/manual/alerts/whitehall-scheduled-publishing.html.md.erb renamed to source/manual/whitehall-scheduled-publishing.html.md.erb

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@ owner_slack: "#govuk-publishing-experience-tech"
33
title: Whitehall scheduled publishing
44
parent: "/manual.html"
55
layout: manual_layout
6-
section: Icinga alerts
6+
section: Publishing
77
---
88

99
## Overdue publications in Whitehall
1010

11-
This alert means that there are scheduled editions which have passed their
11+
Sometimes there may be scheduled editions which have passed their
1212
publication due date but haven't been published by the scheduled publishing
1313
workers. Scheduled publishing is performed by Sidekiq workers picking up jobs
1414
from a scheduled queue.
@@ -37,11 +37,11 @@ following:
3737

3838
If the above rake tasks aren't working, it could be because the database was
3939
recently restored, perhaps due to the data sync. In that case, you can try
40-
running the following Rake task on a `whitehall_backend` machine:
40+
running the following Rake task:
4141

4242
<%= RunRakeTask.links("whitehall-admin", "publishing:scheduled:requeue_all_jobs") %>
4343

44-
Due to the overnight [data anonymisation process](https://github.com/alphagov/whitehall/blob/7b5c5a086b89cb62ffba62b152a0a8dcfc10c8e6/script/scrub-database) you may notice
44+
Due to the overnight [data anonymisation process](https://github.com/alphagov/govuk-helm-charts/blob/20a96dd5/charts/db-backup/scripts/whitehall.sql) you may notice
4545
that some of the pending documents have one or more edition that is in a
4646
`scheduled` state, is `access_limited`, and may have one or more attachments
4747
with the filename `redacted.pdf`.
@@ -54,8 +54,8 @@ the same documents/editions.
5454

5555
## Scheduled publications in Whitehall not queued
5656

57-
This alert means that the number of editions in the database which are
58-
scheduled to be published in the future is different from the number currently
57+
It is also possible for the number of editions in the database which are
58+
scheduled to be published in the future to be different from the number currently
5959
in the queue.
6060

6161
Run the `publishing:scheduled:requeue_all_jobs` Rake task to requeue all

0 commit comments

Comments
 (0)