Bug: "level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:980","plugin_id":"focalboard"}

[osbama]

Steps to reproduce the behavior

Install focalboard plugin 7.11.3 or 7.11.4 to Omnibus-deployed mattermost (current as of Oct 2023) Try to open focalboard

Expected behavior

See the boards

Screenshots (optional)

An error message, that asks me to join a private board, although I am the admin.

Edition and Platform

• Edition: Mattermost Boards (plugin)
• Version: 7.11.3 or 7.11.4
• Browser and OS: Firefox

Additional context (optional)

Logs: "level":"info","msg":"Focalboard server","caller":"app/plugin_api.go:977","plugin_id":"focalboard","version":"7.11.4","edition":"plugin","build_number":"6303496202","build_date":"\"Mon Sep 25 18:44:10 UTC 2023\"","build_hash":"c120e124551313a32856062a45c94eb67c36c445" ,"level":"info","msg":"Boards product successfully started.","caller":"app/plugin_api.go:977","plugin_id":"focalboard"}

"level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:980","plugin_id":"focalboard"

Also: "level":"warn","msg":"Unrecognized config permissions tag value.","caller":"api4/config.go:431","tag_value":"sysconsolewrite*_read"}

Might be related: "level":"warn","msg":"Error while creating session for user access token","caller":"app/session.go:90","error":"createSessionForUserAccessToken: Invalid or missing token., resource: UserAccessToken id: token=***

[DerekJarvis]

This bug is still happening in 2024 on version 8.0.0 . Has a solution been found?

[DerekJarvis]

I found the problem and solution. focalboards doesn't do a very good job of cleaning up user preferences stored in the browser. It stores lastViewId and lastBoardId in your local data. When you migrate to a new instance, or delete a board, it doesn't clear out these preference and always tries to query /boards/<board_id>/blocks?all=true to get information about the board. The API returns that the board doesn't exist, and sometimes erroneously prompts you to try to join the board (that doesn't exist).

So to fix this, just clear your site preferences.

Also, make sure you don't refresh too quickly while troubleshooting. The default rate limit is set pretty low, and boards requires 10-15 queries to load up a page. A few refreshes and you're 429 rate limited, and then the whole app becomes unstable.