Skip to main content
Warning This document has not been updated for a while now. It may be out of date.
Last updated: 23 Sep 2020

Debug published documents with incorrect links

This can happen when the Publishing API is still working through all of the pages that may have changed due to dependency resolution. You can find out if this is a problem by monitoring Publishing API sidekiq queue and seeing if the downstream_low queue is high.

To get things processed faster you can run the following Rake task on the Publishing API in Jenkins, represent_downstream:high_priority:content_id['some-content-id some-other-content-id'], which will re-represent them downstream via the high priority queue.