robchur wrote:

It's not supposed to; the data comes out of the link tables, which aren't
rebuilt upon purges. Either do a null edit or wait for the job queue to update
the template links table.

robchur wrote:

(In reply to comment #1)

or wait for the job queue to update the template links table

Ignore this bit, it's not applicable.

So how quickly might one expect them to be rebuilt? They have been at
least several hours out of date that I have seen.

robchur wrote:

As I've explained above, a null edit is required to cause a link table update.

Okay, then is there some reason why a purge request shouldn't be made to
also update the relevant portion of the link table?

robchur wrote:

"Purge" means "purge caches" - link tables aren't a cache. I don't think it
would be a brilliant idea to cause link table updates on purges, to be honest,
given the current rate at which our users apply "purge it" as a fix-everything.

You mean it doesn't fix everything? ;-)

I had always assumed that purge was functionally equivalent to a null edit in
terms of rebuidling the page without the bother of a log entry. Learning that
it is not strikes me as suprising behavior.

robchur wrote:

No, not at all. A purge merely touches the page record so that existing parser
caches of it will be cleared for all users.

Link tables and other "relationship" information is updated when a page is saved.