Per @rtibbles this should be fixed in #7766 (a closed issue) in 0.14.7 - so:
On the UNW online servers, updates are showing on the Device tab immediately after the import finishes, but there's a long delay before they show on the Learn page.
Reported by Penny from UN Women:
When updating the channel on the [India] server, it takes a long time for updates to appear on the Learn tab. My last update of the Second chance channel took 45 minutes for the changes to appear. The strange thing is that the updated version is shown immediately on the Device tab, but then there’s this very long wait for it to display on Learn. The updates do not involve massive or resource-heavy changes. I’ve had this delay problem before when importing to the Mexico server
…
Tell us about your environment, including:
Note that this should be fixed in 0.14.7 by this PR: #7766
Looks similar to #4463
Looks similar to #4463
It's slightly different, as #4463 is a case where import was interrupted by power failure, and we currently have no way in the UI for a user to recover from this intermediary state. The issue here is probably that the cache invalidation was not working as intended.
Update from Penny as this seems to still be persisting:
It raised its head again this morning when I was importing new content (two new topics) for the Segunda oportunidad con el apoyo de Pro- México & Prosociedad channel on the Mexico server. It took over an hour for the imported resources to display in Learn, after they were visible in the Device tab. I know the 0.14.7 upgrade was due to have resolved this, hence the issue in Notion being marked as complete.
Following the update from Penny that the issue was persisting, she tried again and had some improved results:
I wanted to report that I imported two new channels to the Mexico server this morning and the delay between import and displaying on Learn was between 7 and 10 minutes for one and a few minutes for the other, so much improved from previously. Those kind of delays are quite acceptable from my point of view. I’ll keep monitoring when I do further imports and let you know.
Thanks for the follow up info, @lauradanforth - sounds like the fixes we put in place had some effect. Possible that intervening caching might be responsible for the remaining delay, but we can double check whether it is similar on a regular Kolibri instance.
Most helpful comment
Following the update from Penny that the issue was persisting, she tried again and had some improved results: