Tested on 5.4.10, but 5.4.11 probably suffers from the same.

How to reproduce:

• have a content type published via a delayed workflow, eg article
• have a page that lists that content, fetching it via Content search then loading its Location
• set an article to delayed publication, wait, run legacy cworkflow script
• view the listing page => error 500, with a Stash error message
• the stash problem comes from the SPI layer finding a Content entity with NULL value for mainLocationId
• which in turn comes from the fact that, when the cronjob runs and publishes content, the PersistenceCachePurger does not clear properly the SPI cache for that content
• which happens because the legacy kernel emits a 'content/cache' legacy event with the correct location Id, but the ez5 kernel can not load that location, and hence does not clear the vontent cache (it uses the location to find its content id)
• this is probably due to the fact that legacy kernel and ez5 kernel use separate db connections, and legacy publish operation has a transaction wrapping it