Content nodes show "Not found" after signing back in without refreshing

[marcusolrik-illumi]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.1.2

Bug summary

After being signed out due to inactivity, logging back in causes content nodes in the tree view to display "Not found. The requested route could not be found." The content only appears after manually refreshing the page, clicking the Recycle Bin in the content tree or changing tabs in backoffice.

Specifics

• Fresh install using dotnet new umbraco --name MyProject
• I created a basic document type with a text field and added it to the content tab.
• A gif demonstrating the issue is attached.

Steps to reproduce

1. Create a new Umbraco project using dotnet new umbraco --name MyProject.
2. Create a simple document type and add it to the content tab.
3. Wait until the session expires and you are automatically signed out.
4. Log back in.
5. Click on different nodes in the content tree.

Expected result / actual result

The content should display immediately when clicking on a node after logging back in, without needing to refresh the page.

---

This item has been added to our backlog AB#49175

[github-actions]

Hi there @marcusolrik!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

Thanks @marcusolrik , I was able to reproduce it on v15.2.0-rc
Exception happens at the _states value in state.manager.ts

[marcemarc]

Yes, our editors have hit this problem too, is there anything that can be done to recover the work when this occurs? if work is unsaved should the logout be prevented? or does that defeat the object of the timeout when a screen is unattended?

[iOvergaard]

This should be fixed by #19495 and is intended to be released in 16.1.