# Failed to insert record to database **URL:** \ **Category:** Troubleshooting\ **Created:** [March 12, 2022, 8:25pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084 "2022-03-12T20:25:50Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 12, 2022, 8:25pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/1 "2022-03-12T20:25:50Z")
```json { "caller": "web/context.go:101", "err_details": "resource: SidebarCategories id: userId=a...", "err_where": "GetSidebarCategories", "http_code": 404, "ip_addr": "1...", "level": "debug", "method": "GET", "msg": "Failed to insert record to database.", "path": "/api/v4/users/a.../teams/a.../channels/categories", "request_id": "a...", "timestamp": "2022-03-12 20:15:32.417 Z", "user_id": "a..." } ``` I experience pretty much the same symptoms as described here: > [@Cant see channels](https://forum.mattermost.com/t/cant-see-channels/10441): > > Helo. After upgrade from 5.25 to 5.27 users cant view channels bar on left. How can i fix this issue? > [@\[Solved\] Channels disappear after upgrading](https://forum.mattermost.com/t/solved-channels-disappear-after-upgrading/12511): > > After upgrading from 5.31 to 5.37, the list of channels disappears from the left sidebar: If I use Ctrl+K to display the channels, only the “recent” ones are displayed — if I type some letters, though, all channels containing these letters are displayed. If I “filter by unread”, the unread channels are displayed, and disappear again when choosing “show all channels”. I tried to revert to 5.31, and the channels reappear, but not when I use Ctrl+K: the list is blank (can’t… [https://docs.mattermost.com/upgrade/important-upgrade-notes.html](https://docs.mattermost.com/upgrade/important-upgrade-notes.html) However, I am using PostgreSQL and the collations have to be correct, because when migrating the database from `9.4` to `14.2`, the `pg_upgrade` check did not succeed, until the `locale` and the `encode` settings were correct. The frustrating part about this situation is that the error is shown in the logs at `debug` level (first mistake) and even when you turn up the level to `DEBUG` in the Mattermost system console, then all you get is _“Failed to insert record to database.”_ as the error message (second mistake). I have no idea, what the cause is. It just says, it’s failing. But why? What’s the problem? I need to fix it. I would appreciate any assistance! ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 12, 2022, 8:38pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/2 "2022-03-12T20:38:26Z")
The offending procedure in the source code: > Line 92 & 101 are the culprit. Insufficient error message + posting it at `debug` level. The procedure calling the problem inducing procedure: > Line 26. The procedure releasing the problem: > The procedure called by its wrapper: > Going down to lower levels: > > > > > > > > > > ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 12, 2022, 9:28pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/3 "2022-03-12T21:28:41Z")
Current state of the database: ```sql SELECT * FROM SidebarCategories; id | userid | teamid | sortorder | sorting | type | displayname | muted | collapsed ----------------------------+----------------------------+----------------------------+-----------+---------+-----------------+-----------------+-------+----------- id........................ | userid.................... | teamid.................... | 0 | | favorites | Favorites | | id........................ | userid.................... | teamid.................... | 10 | | channels | Channels | | id........................ | userid.................... | teamid.................... | 20 | recent | direct_messages | Direct Messages | | ``` ```sql SELECT * FROM SidebarChannels; channelid | userid | categoryid | sortorder -----------+--------+------------+----------- (0 rows) ``` ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 12, 2022, 11:14pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/4 "2022-03-12T23:14:12Z")
I tried out every non-modifying SQL statement from all the procedures manually and they all worked, as they should. I did not see any indication, why anything would fail. I’m very sure, this is where the actual error originates from: > > At least, that must be the case, because only this fits the error message from the log. If it were in a different place, the error message from the log would be slightly different. @hmhealy Could you please assist? ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 13, 2022, 2:06am UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/5 "2022-03-13T02:06:35Z")
I have set up a new Team on the same server. Everything works. I have set up a Mattermost Preview server. Everything works. I have duplicated the table rows to fit into the original Team. The way the rows’ values are filled are precisely the same, as with the working Team and with the working server. Still, even when everything is exactly the same, it still won’t work for the original Team. ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 13, 2022, 5:32pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/6 "2022-03-13T17:32:52Z")
I managed to finally solve it. The error message provided by the Mattermost Server was not only insufficient, but also **false**. There was no error inserting anything into the database. The SidebarCategories could not be fetched and sorted. That was the issue. Whenever you reload the page or try to create a new category in the sidebar, the `SELECT` statement, which tries to gather all existing categories with their channels or channel IDs, will fail, because the semantics changed between Mattermost Server versions. To fix it for your Mattermost Server, this is what you have to do: (Kept the SQL statements very simple, so every user can understand, even without any database knowledge.) ```sql SELECT * FROM SidebarCategories WHERE (SidebarCategories.UserId = 'myuserid' AND SidebarCategories.TeamId = 'myteamid'); ``` You get a result like the following: ```sql id | userid | teamid | sortorder | sorting | type | displayname | muted | collapsed ----------------------------+----------------------------+----------------------------+-----------+---------+-----------------+-----------------+-------+----------- id........................ | userid.................... | teamid.................... | 0 | | favorites | Favorites | | id........................ | userid.................... | teamid.................... | 10 | | channels | Channels | | id........................ | userid.................... | teamid.................... | 20 | recent | direct_messages | Direct Messages | | ``` First, you need to makre sure the IDs of the official Mattermost categories are upgraded. In earlier versions, the IDs were custom strings, which were randomly generated, just like with custom categories. I.e., they look like this: `sfkjhdgsfkljhdgfkjhdfg` However, newer Mattermost versions generate the ID by the following pattern: ```auto _userid_teamid ``` So, if you are looking at the previous table result: ```auto id | userid | teamid | sortorder | sorting | type | displayname | muted | collapsed ----------------------------+----------------------------+----------------------------+-----------+---------+-----------------+-----------------+-------+----------- ........ | userid.................... | teamid.................... | 0 | | favorites | Favorites | | ......... | userid.................... | teamid.................... | 10 | | channels | Channels | | .. | userid.................... | teamid.................... | 20 | recent | direct_messages | Direct Messages | | ``` You need to update the IDs of each category. ```sql UPDATE SidebarCategories SET id = '........' WHERE id = 'favorites_myuserid_myteamid'; UPDATE SidebarCategories SET id = '.........' WHERE id = 'channels_myuserid_myteamid'; UPDATE SidebarCategories SET id = '..' WHERE id = 'direct_messages_myuserid_myteamid'; ``` Now, the table should look like this: ```sql id | userid | teamid | sortorder | sorting | type | displayname | muted | collapsed ----------------------------+----------------------------+----------------------------+-----------+---------+-----------------+-----------------+-------+----------- favorites_myuserid_myteamid | userid.................... | teamid.................... | 0 | | favorites | Favorites | | channels_myuserid_myteamid | userid.................... | teamid.................... | 10 | | channels | Channels | | direct_messages_myuserid_myteamid | userid.................... | teamid.................... | 20 | recent | direct_messages | Direct Messages | | ``` It may also be the case, that the `sortorder` column has invalid values. In that case you **need** (this is mandatory!) make sure, that each row has a unique `sortorder` value. There must not be any duplicates. So, let’s say you have `sortorder` column, where the Favorites category and the Channels category have the same value in the `sortorder` column, you need to update those values to be distinct. ```sql UPDATE SidebarCategories SET sortorder = 0 WHERE id = 'favorites_myuserid_myteamid'; UPDATE SidebarCategories SET sortorder = 10 WHERE id = 'channels_myuserid_myteamid'; ``` Correct: ```sql id | userid | teamid | sortorder | sorting | type | displayname | muted | collapsed ----------------------------+----------------------------+----------------------------+-----------+---------+-----------------+-----------------+-------+----------- favorites_myuserid_myteamid | userid.................... | teamid.................... | 0 (ok) | | favorites | Favorites | | channels_myuserid_myteamid | userid.................... | teamid.................... | 10 (ok) | | channels | Channels | | direct_messages_myuserid_myteamid | userid.................... | teamid.................... | 20 (ok) | recent | direct_messages | Direct Messages | | ``` Wrong: ```sql id | userid | teamid | sortorder | sorting | type | displayname | muted | collapsed ----------------------------+----------------------------+----------------------------+-----------+---------+-----------------+-----------------+-------+----------- favorites_myuserid_myteamid | userid.................... | teamid.................... | 0 (ok) | | favorites | Favorites | | channels_myuserid_myteamid | userid.................... | teamid.................... | 0 (duplicate!) | | channels | Channels | | direct_messages_myuserid_myteamid | userid.................... | teamid.................... | 20 (ok) | recent | direct_messages | Direct Messages | | ``` Now, to the last column of this table. I’m not sure, if adding a `sorting` value is mandatory, but just let’s add it, to be sure: ```sql UPDATE SidebarCategories SET sorting = 'manual' WHERE id = 'channels_myuserid_myteamid'; ``` Set this for every category, except `direct_messages`, which stays as `recent` and `favorites`, which does not need one. So far, we are done with the `SidebarCategories` table. Next is `SidebarChannels`. Let’s have a look: ```sql SELECT * FROM SidebarChannels; ``` Might look something like this: ```sql channelid | userid | categoryid | sortorder ----------------------------+----------------------------+----------------------------------------------------------------+----------- (0 rows) ``` It’s empty. We need to add the channels to the `channels` category. We will add all channels to that category, because once everything works, you can re-order and re-assign in the Web UI, anyway. Let’s see what channels are available, in the first place: ```sql SELECT * FROM Channels WHERE teamid = 'myteamid'; ``` Could look like this: ```sql id | createat | updateat | deleteat | teamid | type | displayname | name | header | purpose | lastpostat | totalmsgcount | extraupdateat | creatorid | sche meid | groupconstrained | shared | totalmsgcountroot | lastrootpostat ----------------------------+---------------+---------------+----------+----------------------------+------+-------------+-------------+--------+---------+---------------+---------------+---------------+----------------------------+----- -----+------------------+--------+-------------------+---------------- myrandomchannelidabc| 123 | 123 | 0 | teamid | O | Town Square | town-square | | | 321 | 0 | 0 | | | | | 0 | 321 myrandomchannelidefg | 123 | 123 | 0 | teamid | O | Off-Topic | off-topic | | | 321 | 0 | 0 | | | | | 0 | 321 myrandomchannelidhij | 123 | 123 | 0 | teamid | O | TEST_2 | test_2 | | | 321 | 0 | 0 | userid | | f | | 0 | 321 (3 rows) ``` We are only interested in the `ChannelId` (`id`) values available. They are enough to identify which channels are available and should be added to the `channels` category: ```sql SELECT id FROM Channels WHERE teamid = 'myteamid'; ``` May result in: ```sql id ---------------------------- myrandomchannelidabc myrandomchannelidefg myrandomchannelidhij (3 rows) ``` For each of these `id` values, you need to add a row into the `SidebarChannels` table, to assign them to a category: ```sql INSERT INTO SidebarChannels(channelid, userid, categoryid, sortorder) VALUES ('myrandomchannelidabc', 'userid', 'channels_userid_teamid', 10); INSERT INTO SidebarChannels(channelid, userid, categoryid, sortorder) VALUES ('myrandomchannelidefg', 'userid', 'channels_userid_teamid', 20); INSERT INTO SidebarChannels(channelid, userid, categoryid, sortorder) VALUES ('myrandomchannelidhij', 'userid', 'channels_userid_teamid', 30); ``` Not how the `sortorder` is correct, as explained previously. You have to apply this process to all members in the Team, because we just used a single `userid` here. If you have several Teams, you need to apply that to the different Teams, as well. All this can be probably solved by creating some huge SQL functions. I described the step by step process, the way I got to the point of fixing the issue. So, I did not start with a huge function to begin with, as I did not know what’s wrong, in the first place. * * * If I did not forget a step, this should be enough to fix the tables. If you reload your Mattermost Web UI (reload the page in the browser), then the Sidebar should properly work, now. * * * * * * To fix this from a Mattermost product quality perspective, this is what you have to do (in no particular order): 1. Improve error messages. Having the error message `Failed to insert record to database` for this kind of scenario is not only insufficient, but also **false**! 2. Do not swallow the actual error messages. As seen in the code examples above, there are so many different error messages, while still too short and unhelpful, they would’ve definitely still helped more than the generic `Failed to insert record to database` which seemingly is used for _any_ database related error. This is a debugging nightmare. 3. Raise all error messages to the `error` level. I shouldn’t have to enable the DEBUG log to see these messages. 4. Improve error handling. Just raising the error through 10 procedures in the call stack does not solve any issue. This is hard to debug (see my wasted time above, in previous posts) and does not help anyone, really. 5. Fix migration. If the migration would’ve worked in the first place, I probably wouldn’t have wasted so many hours in the first place debugging this, if the migration would’ve worked to begin with. 6. STOP DEPENDING ON `sortorder`!!! Why is `sortorder` absolutely mandatory? Do not make it mandatory. If some `sortorder` values are duplicates, then fix them and the user can re-order the channels in the UI. Boom, done. Everything works. Stop making an elephant out of a warning type of situation. Just fix the `sortorder` for all entries and we are done. No need to break an entire feature just because the `sortorder` values are not entirely correct. 7. Improve documentation. Oh, how it would’ve helped if the code were properly documented. In hundreds of lines of code I have read, I have seen like 3 or 2 short sentences as comments. That’s it. You need to explain the code in such a project. Especially important in open source projects. How would a majority of people start contributing, if there are no "why"s explained. By having so little documentation, already the vast majority of FOSS contributers are excluded from supporting and improving. ---
**Author:** ![amy.blais](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/amy.blais/32/7481_2.png) [@amy.blais](https://forum.mattermost.com/u/amy.blais)\ **Post date:** [March 14, 2022, 1:05pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/7 "2022-03-14T13:05:19Z")
> [@Akito](#): > > To fix this from a Mattermost product quality perspective, this is what you have to do (in no particular order): > > 1. Improve error messages. Having the error message `Failed to insert record to database` for this kind of scenario is not only insufficient, but also **false**! > 2. Do not swallow the actual error messages. As seen in the code examples above, there are so many different error messages, while still too short and unhelpful, they would’ve definitely still helped more than the generic `Failed to insert record to database` which seemingly is used for _any_ database related error. This is a debugging nightmare. > 3. Raise all error messages to the `error` level. I shouldn’t have to enable the DEBUG log to see these messages. > 4. Improve error handling. Just raising the error through 10 procedures in the call stack does not solve any issue. This is hard to debug (see my wasted time above, in previous posts) and does not help anyone, really. > 5. Fix migration. If the migration would’ve worked in the first place, I probably wouldn’t have wasted so many hours in the first place debugging this, if the migration would’ve worked to begin with. > 6. STOP DEPENDING ON `sortorder` !!! Why is `sortorder` absolutely mandatory? Do not make it mandatory. If some `sortorder` values are duplicates, then fix them and the user can re-order the channels in the UI. Boom, done. Everything works. Stop making an elephant out of a warning type of situation. Just fix the `sortorder` for all entries and we are done. No need to break an entire feature just because the `sortorder` values are not entirely correct. > 7. Improve documentation. Oh, how it would’ve helped if the code were properly documented. In hundreds of lines of code I have read, I have seen like 3 or 2 short sentences as comments. That’s it. @agnivade @streamer45 @hmhealey @isacikgoz Pinging you for visibility if there are any items here we could open tickets for. ---
**Author:** ![agnivade](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agnivade/32/3846_2.png) [@agnivade](https://forum.mattermost.com/u/agnivade)\ **Post date:** [March 15, 2022, 6:19am UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/8 "2022-03-15T06:19:56Z")
@Akito - Thank you for the great feedback and sorry for all the debugging work you had to do! I completely agree about the error swallowing/improve error messages part. I’ll see if I can create some issues for that. But I am curious to know why did this issue happen in the first place. From what I understood, you upgraded your Postgres server from 9.4 to 14.2 and upgraded the Mattermost version as well? And somehow the migration failed? Do you have any error message from the migration failure? If there is a bug in the migration somewhere, we definitely need to fix that. ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [March 15, 2022, 10:45am UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/9 "2022-03-15T10:45:08Z")
> [@agnivade](#): > > But I am curious to know why did this issue happen in the first place. From what I understood, you upgraded your Postgres server from 9.4 to 14.2 and upgraded the Mattermost version as well? I am currently in the process of migrating my server apps from a standard installation to Kubernetes by Helm Chart. One of those apps was Mattermost Team Edition. Before doing the actual upgrade/migration, I noticed that the database version on the Mattermost instance is 9.4, which is way too old. I would like it to be at the very least on 11, to stay at least a bit up to date. I looked at the default version in the Helm Chart and saw, that the newest PostgreSQL version was the default, so I decided to migrate the 9.4 initialised database to 14.2. I have experience with that and it usually works well, because PostgreSQL database upgrades go pretty well, once you get the gist of what must be taken care of. I am still under the impression, that Mattermost would’ve just kept running under PostgreSQL 9.4, if I wouldn’t have upgraded myself. Please, correct me, if I’m wrong. I assumed, that Mattermost would detect all legacy database structures and automatically migrate them, as this is usually the case with such apps, according to my experience. From what I know, this should be the case with Mattermost. It has a `db_migrations` table and it lists changes made, by version number. > [@agnivade](#): > > And somehow the migration failed? Do you have any error message from the migration failure? I did not see any noticable log messages during the first run, so I dismissed them. I also did not notice anything going wrong, until I realised that the missing channels in the sidebar are actually a bug, rather than me misunderstanding the new version with its new features. > [@agnivade](#): > > If there is a bug in the migration somewhere, we definitely need to fix that. Indeed, it seems like that. The way I fixed it, it was only related to the database tables `SidebarCategories` and `SidebarChannels`. If I understood the upgrade notes correctly, then these were added completely anew in 6.x. I currently cannot find the specific line/place where the additiona was mentioned. I read it somewhere in the documentation or some notes from Mattermost, though. [https://docs.mattermost.com/upgrade/important-upgrade-notes.html](https://docs.mattermost.com/upgrade/important-upgrade-notes.html) * * * If you need any database tables or whatever debug information, you can tell me which to extract. The problem with logs is though, that they are ephemeral by nature. I cannot restore the logs from days ago. However, I watched them closely after finding out, that the sidebar is not working correctly and the only error (at `debug` level) I ever saw was this `Failed to insert record to database` error, which I previously mentioned. Anything else were just `debug` messages, that looked very boring and very `200 OK` like, so it seemed like there was nothing else wrong, judging from the logs. Would be curious to see, what the logs did say during the migration by the server itself, but these logs do not exist, anymore. (Except the server has an extra log, I don’t know of.) If you really cannot reproduce the same issue, I still have the old 9.4 database backed up. ---
**Author:** ![curiouser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/curiouser/32/6247_2.png) [@curiouser](https://forum.mattermost.com/u/curiouser)\ **Post date:** [January 13, 2023, 9:29pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/10 "2023-01-13T21:29:42Z")
Have you attempted any further upgrade (to v7 for example)? I have the same problem (I think I started on postgresql 10, upgraded to 12 and now trying to upgrade mattermost from 5.31.9). I don’t want to put too much effort into solving the problem as you did if there are still underlying issues that continue to wreak havor. ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/akito/32/4090_2.png) [@Akito](https://forum.mattermost.com/u/Akito)\ **Post date:** [January 13, 2023, 10:59pm UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/11 "2023-01-13T22:59:54Z")
> [@curiouser](#): > > Have you attempted any further upgrade (to v7 for example)? The instance wasn’t used for a while, though after a couple of minor fixes, I remember it working fine, as far as I was able to tell as a simple administrative user of the system. > [@curiouser](#): > > I don’t want to put too much effort into solving the problem as you did if there are still underlying issues that continue to wreak havor. If you are fine having it work well enough, then it should be fine, I think. If you need a truly highly professional & important Production Setup, I would recommend just setting it up, again. ---
**Author:** ![curiouser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/curiouser/32/6247_2.png) [@curiouser](https://forum.mattermost.com/u/curiouser)\ **Post date:** [January 14, 2023, 4:40am UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/12 "2023-01-14T04:40:38Z")
Thanks @Akito for posting your debugging and solution as I would never have solved this for myself. Ultimately, I discovered that I had previously attempted in-place upgrades that must have failed (at least partially) - this is judging by the `db_migrations` table contents. I think I may have arrived at a simpler solution for those that don’t mind trashing prior sidebar customizations: `TRUNCATE SidebarCategories; TRUNCATE SidebarChannels;`. The app will insert the appropriate records the next time a user fetches these. Now, the above fixed the problem of no channels in the sidebar, but I actually had trouble with upgrading to v6 and beyond with the app crashing with an error message about “lastrootpostat does not exist”. For this, I found that I could truncate the migrations table, reset the schema version to 5.25 (must have been my initial install version) and then running the app on version 5.39 (last v5) and then upgrading to v7 had things working fine. I also had a single channel where `totalmsgcountroot` was NULL and received an error there, not sure where that came from. All in all: 1. psql updates to rollback migration state and truncate sidebar tables ```sql TRUNCATE db_migrations; TRUNCATE SidebarCategories; TRUNCATE SidebarChannels; UPDATE Systems SET value = '5.25.0' WHERE name = 'Version'; UPDATE channels SET totalmsgcountroot = 0 WHERE totalmsgcountroot is NULL ``` 2. Start the mattermost server running 5.39 to perform all v5 migrations 3. Start the mattermost server running v7 to perform all v6 and v7 migrations ---
**Author:** ![yanuk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/yanuk/32/6348_2.png) [@yanuk](https://forum.mattermost.com/u/yanuk)\ **Post date:** [August 14, 2023, 3:02am UTC](https://forum.mattermost.com/t/failed-to-insert-record-to-database/13084/13 "2023-08-14T03:02:54Z")
I had the same problem of missing sidebar and this solved my issue! In my case, I migrated from Postgres 10 to 15 running MM 7.10.5 (I was prepping to upgrade to MM V8 since Postgres 10 wasn’t supported). I want to add that any errors in the channelsidebar and channelmembers tables also caused the user not being able to load the team on default eg: going to [chat.website.com](http://chat.website.com) doesn’t load, a team selection page will appear with no teams to load. [chat.website.com/myteam](http://chat.website.com/myteam) would load (but with empty sidebar) because of the error in the database. Solving the sidebar solved the team selection page as well.