When I try to update to 3.6 on our test site and then restore a recent backup, I get error messages related to themes (such as full-name-in-mentions and cookie-banner).
I assume this is because API paths have changed.
These errors persist even when I update the theme components (automatically via rake themes:update).
When I visit the site some hours later, the errors are no longer displayed and the themes work.
ask.discourse.com tells me, that it is common for theme update to come live later due to caching and background jobs but lacks to give me a pointer, where I can read more about this behavior.
I tried to get rid of caching issues by restarting the staging sites docker without success.
How could I wait for updates coming online in my script?
Should I restore the current backup before rebuilding the staging site?
Update: Restoring the backup before container rebuild does not change the situation.
However, if I change the URL to the repo via command line, a direct rebuild of the theme component seems to be triggered, and the error disappears.