Probably due to use of slave server; the change is made on master and the list is pulled from slave during the same request. With the slave connection already open, it's going to give data from before the change.

A simple change that might help would be to run an HTTP redirect to force a clean reload instead of showing back the list in the same request handler. That might still show you old data if the slave is lagged a bit, but it would probably usually work correctly. Would have the added bonus that hitting 'reload' won't prompt about POST data, which everyone hates.

Done in r24210