Time Warp cannot load on parent and child sub tab at the same time in Console App

[gstoevelaar]

I have some users who regularly gets the error 'time warp cannot load on parent and child sub tab at the same time error'. Most of the time when they visit an open tab with this component after a couple of hours, but sometimes also random.

We have placed the timewarp component on the account record page and on the asset record page and are using console navigation in this App. They open regularly these kind pages and it's not optimal for them to refresh everytime the component when the user gets this message. Is there something to do to minimize these messages or are there any changes in the pipeline to solve/minimize this problem?

Kr,
Gert Stoevelaar

[deejay-hub]

Hi @gstoevelaar. We have a known issue when using Time Warp in a console app. It has been reproduced when using the component in an object opened as a sub tab of another

Here we asked to open Cases as a sub tab of Contact. If I put Time Warp on the Contact page then I will see the Case page opened as the sub tab but when I navigate back to the Contact I see this error as you say.

This happens because the page with Time Warp on is not shown immediately.

One way to mitigate the issue would be to move Time Wapr into a sub tab on the page. So for the example above we created a sub tab on the Contact details page called 'Engagement' then added Time Warp here. This means the component isn't loaded until a user clicks on it (this assumes the tab isn't the default one).

This is generally a better design since the default tab should only contain minimal info to improve page load times. Optional - nice to have info - should move to a sub tab. That way the data isn't queried until needed.

I hope that helps.

If your use case is different let us know. Ideally steps to recreate the issue work best for us.

[gstoevelaar]

Hi @deejay-hub, I will suggest to the users to put the component under a tab.
Thanks for your quick reaction.

Kr.
Gert