Help with publishing content
When a department is publishing content that is high priority, it may be necessary to help them to ensure it goes out as smoothly as possible.
Read what to do if a publisher is complaining that a document isn’t live on GOV.UK after publishing it.
You might see documents being published but links not updating if the format is still showing as “Coming Soon” on some pages.
You may need to clear the Varnish or Fastly caches if the content is not showing on the live site quick enough.
If it looks as though emails haven’t been sent out for a publication, there should be an alert about unprocessed content changes and there is guidance on how to solve this.
If there are no alerts, it would suggest that the content change never made it
to the Email Alert API. In which case, you should check that Email Alert
Service is correctly consuming from RabbitMQ.
If all looks fine, it may be necessary to manually create a
Email Alert API.
We have an alert that checks that email alerts for Travel Advice and Medical Safety Alerts go out correctly. Although an alert won’t be triggered for other kinds of documents, the guidance will still apply.
- If a scheduled publication hasn’t gone live, start here: if documents aren’t live after being published. If it looks as though the content was never published from Whitehall, there is a Rake task available which will publish overdue documents. In Production, run this Rake task.
$ bundle exec rake publishing:overdue:publish