Okay. Should we put this ticket on the sprint board?

This seems to be easier to reproduce when logged out. I'm not sure which is significant, creating the topics logged out, or that the first view is logged out.

I can't seem to figure this out.

I know it's an intermittent problem caused by a premature cache-filling operation, and I know various secondary information like the keys, etc. but despite a lot of conditional breakpoints I can't figure out what triggers the premature cache-fill.

I'm ready to use a workaround, but I'm hoping it actually works. I'm concerned that if something like the job queue or a deferred update is triggering the premature cache fill (maybe due to slave lag), purging the cache won't really help. The cache would be empty at the end of the conversion operation (which I think it already normally is), but that doesn't necessarily prevent the job queue or something from doing a premature cache-fill.

So the best solution may be to trigger a cache fill ourselves.

Change 219602 had a related patch set uploaded (by Mattflaschen):
Fix topics not appearing reliably after LQT->Flow, before action=purge

https://gerrit.wikimedia.org/r/219602

Change 219602 merged by jenkins-bot:
Fix topics not appearing reliably after LQT->Flow, before action=purge

https://gerrit.wikimedia.org/r/219602

• https://gerrit.wikimedia.org/r/219602 (branch master): WMF-deploy-2015-06-23_(1.26wmf11)

General check for LQT->Flow import and purge(on ttp://test.wikimedia.beta.wmflabs.org/wiki/) - all topics were timely&properly displayed.