On a local government website running Craft CMS a lot of in-body links are effected with the Link to an Entry function within the Redactor editor. I have encouraged the content editors to use this instead a directly coded URL on the basis that if the linked-to entry changes location the link will still work. So far so good until sometime in the last week around 140 of these internal links corrupted.

So what used to be

<p>Please see <a href="/council/publications/files/schedule-of-fees-and-charges#entry:1378:url">Schedule of fees and charges</a>


<p>Please see <a href="{entry:1378:url}#entry:1378:url">Schedule of fees and charges</a>

and of course no longer work.

Understandably there is a lot of upset, both around the fact that access to important documents is no longer available, and that fact that someone has to find and repair 140 links, and then check that they were repaired correctly.

Can anyone offer any suggestion as to how this may have happened? All I can offer is that a Pending Task held up the task list for a while (I don't know how long). The task hadn't failed but after seeing no action on it for a day or so, I deleted it and this caused a backlog of tasks to run. While I don't know if there was any connection, but the timing of the start of the problem does match the running of the tasks.

The links have also been changed in all the entry revisions. At first this made me suspicious that they were never right, but as we run a link checker looking for broken links around once a month, or whenever a bigger set of edits have been made, I can confirm that this change happened recently. This points me back to the tasks.


1 Answer 1


It's entirely possible it was the stuck tasks depending on how the task originally failed, how many (and which ones) were backed up behind it and how many (and what kind of) changes were made on the site while the tasks were stuck.

Hard to know with 100% confidence, though.

  • Thanks Brad. I've narrowed the timing down to the same day the tasks were run. One correction: the blocking task had a status of "running". I restored from an overnight backup, and this time deleted all the backup tasks before deleting the blocking one so as not to have a repeat episode. I suppose the other problem I have to address is that stuck tasks are a regular thing for this site. They don't always show as failed but never go anywhere. Commented Mar 3, 2016 at 3:54
  • You can use this as a general starting point for debugging stuck tasks: craftcms.com/support/stuck-tasks
    – Brad Bell
    Commented Mar 3, 2016 at 6:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.