Litium UI never updates after operations complete in 8.3.1

We have a problem in 8.3.1 that the Litium UI never updates after operations complete in Litium Cloud behind Fastly. In development it works like it should.

Could this be Bug 60412 Server sent events have a default timeout that is longer than Fastly default timeout?

When running Litium behind Fastly the timeouts need to be adjusted either in platform or in the configuration for Fastly to avoid missing update events to the UI.

We are running Litium behind Fastly.

The problem affects large parts of the UI. For example,

  • When adding categories in PIM, page needs to be reloaded for tree on the left to update
  • When adding pages in CMS, page needs to be reloaded for tree on the left to update
  • Product import operations just hang with the “importing” modal/lightbox/alert and no updates, but page reload shows that import has taken place

If it’s 60412, the mitigation says

Litium:ServerSentEvents.KeepaliveInterval can be used as the configuration key to configure the keepalive interval in Litium.

Not sure what to set this to to mitigate the problem.

If it’s not 60412, what could it be?

Litium version: 8.3.1

In 8.4 the default timeout is now set to 9 sec so try to set it to 9 sec since default is 30 sec in your version or upgrade your solution would also be a good choice.

Thank you. I agree about upgrading. But I’m not sure this is bug 60412 so an upgrade feels like the wrong quick-fix.

Applying the below appSetting seems to have resolved the problem:

{
    "Litium": {
        "ServerSentEvents.KeepaliveInterval": 9,

Don’t really understand why it works though. The problem doesn’t appear after 9 or 30 seconds, the problem appears instantly, in that the UI doesn’t update at all for “asynchronous” operations. Adding a PIM category takes less than a second for the left-hand category tree in the UI to update, for example, but without setting the keep-alive interval it never updates. And the product import progress bar doesn’t update at all without the interval setting.

Upgrade first and test if it resolves the issue, if not report a bug with needed steps for how we can reproduce it on latest version thanks.

Thank you. Applying the above appSetting seems to have resolved the problem. So everything is working now.

We will upgrade at some point, to resolve the issue permanently.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.