[Bug] Toast message Spam: Session status hydration timeout after 5000ms

[asaprajx]

What happened?

After updating to version 2026.8.1, whenever I open PawWork, there's always a pop-up toast message saying failed to reload pawwork, and after every time an assistant completes its response, it spams the right status bar with a similar toast, saying Failed to reload Workspace. There are no functional bugs, but it feels annoying and it started after the updating to v2026.8.1.

Which area seems affected?

Not sure

How much does this affect you?

Minor issue or polish

Steps to reproduce

1. Open Pawwork; see the first toast.
2. Let an assistant finish its task or interrupt in between the task execution; see the other toast message.

What did you expect to happen?

I didn't expect anything; I have a good PC with mid-high-end specs, so I think it's not that my PC isn't capable of running PawWork. I think PawWork should open and operate without the toasts as it used to be

PawWork version

2026.8.1

OS version

windows 11

Can you reproduce it again?

Yes, every time

Diagnostics

here are some screenshots regarding this issue,.

[webbrain-one]

Thanks for the detailed report! I’ve opened a pull request to address this: #1556.

The fix targets the session status hydration timeout that was triggering the recurring "failed to reload" toast messages. It should prevent the spam on app launch and after assistant responses. Feel free to take a look or test it out, and let me know how it goes. Thanks again for flagging this! 🚀

[Astro-Han]

Hi @asapjayz, thanks for the detailed report - the screenshots and repro steps made this easy to track down.

The root cause: on app launch and after each assistant turn, the app re-fetches the full session status snapshot with a 5-second budget. On your machine that fetch regularly took longer, and each timeout was wrongly shown as a "Failed to reload Workspace" error toast - even though nothing was actually broken and the data caught up on its own a moment later. That's why you saw no functional bugs, just the spam.

Fixed in #1560: a timed-out status snapshot now degrades quietly (still logged as a diagnostic) instead of popping the error toast. The fix is merged and will ship in the next release. Sorry for the noise, and thanks for helping us catch it!