500 Internal Server Error on Grouping/Duplicating - Cloud Workspace Locked

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

SaaS

What are the exact steps to reproduce this issue?

  1. Log into a workspace hosted on Baserow Cloud (api.baserow.io).
  2. Open a specific table (e.g., Table ID: 998446).
  3. Attempt to apply a ‘Group by’ rule to any column in a Grid View.
  4. The UI immediately throws a generic “Action not completed” popup.
  5. Checking the browser DevTools Network tab reveals a hard 500 Internal Server Error on the POST request to https://api.baserow.io/api/database/views/1958379/group_bys/.
  6. Attempting to bypass the view by duplicating the entire table (with or without data) results in another 500 Internal Server Error on the POST request to https://api.baserow.io/api/database/views/table/998446/.
  7. This same 500 error is now happening when trying to group columns on a completely separate table in the same workspace.

It appears the backend database schema/index for these tables has become corrupted or locked on the server side, preventing any structural changes or grouping queries from executing.

Attach screenshots, videos, or logs that demonstrate the issue.

cbc23554-a00d-4506-bd2a-31a13db1fde5.png
cbc23554-a00d-4506-bd2a-31a13db1fde5.png435×186 14.7 KB
10f74e12-3fed-4cce-b253-921dfb30bdc5.png
10f74e12-3fed-4cce-b253-921dfb30bdc5.png1061×984 224 KB

2

Hello @hsalehi,

Please accept my apologies for the inconvience - there’s a good chance this was due to our database migration, we had to put Baserow into a read-only mode for a short time in the early hours (UTC) of Saturday morning.

If you are based in the Americas (judging by your macOS clock) then those errors were due to the maintenance window.

Should this happen again please don’t hesitate to get in touch!

Cheers,
Peter