Something very strange happened today with our Supabase SQL. For a period this morning, we were getting a 400 response from the API, claiming our admin user did not have access to the items we were trying to get from the API. This admin user has full admin access to everything. Also, neither myself nor my client are able to access any of these items either, and my client truly has access to everything.
Is there a chance there was a strange event with the API today that would have caused this? If not, perhaps someone could DM me and I could hand over a Record ID and possibly get some more information about it to diagnose further? We’re really failing to understand how neither of our 3 user accounts have access to these items that produce record.update webhooks.
Thanks a lot for taking the time to report this issue in such detail. We really appreciate it!
We’ve already checked our logs, and so far we haven’t been able to spot any irregularities in the API usage or the API error logs that would explain these 400 responses. One possibility we suspect is that the affected items might have been soft-deleted records; sometimes this can trigger access issues that look like permission errors, even for admin users.
But we definitely want to double-check the exact records. If you could DM me a Record ID, we’ll trace them specifically in our backend and see whether we can identify any inconsistencies or edge cases that might have caused this.
For the record, this was completely my fault and huge thanks to @Leo and @Tim for helping me crack it. We’re all so lucky to have this amazing community to help us through all of these issues to build the best systems we possibly can!