Skip to content

Office Hours · Case file Nº 27

Debugging& RLS

Heard on
May 26, 2026
Case officer
Sam
Filed under
Beginner
In attendance
62

Case summary

A beginner session (a repeat of a popular topic) covering debugging fundamentals and a light intro to RLS. Sam ran a ~25-minute screen-share walkthrough — opening DevTools, reading HTTP status codes, copying error responses into the builder, the redeploy-with-a-space fix, version-history revert, and Canvas arrows for visualising bugs — then a CRUD/RLS primer at entity level, followed by a long open Q&A.

  1. Debugging 101
  2. HTTP status codes (Sam's rule of thumb)
  3. "Function not deployed" fix
  4. Reverting
  5. Canvas for visualising bugs
  6. RLS = Row Level Security
  7. Rate limits & email

Front-desk memos

Notices read into the record

6 notices logged alongside the case.

  • Week schedule

    Tomorrow (Wed): open drop-in. Thursday: the new Testing Agent reveal session.

  • Amsterdam in-person event — 11 June

    A Super Agent session with pizzas and drinks. Sign up via the Luma link.

  • Custom login at 50% rollout

    Possibly scaling to 100% imminently. New apps only; backporting to existing apps is being worked on.

  • Testing Agent rolling out this week

    Going to power users, ambassadors and moderators this week; public release targeted for ~next week.

  • "Branches" teased

    A git-like dev/prod environment within Base44 (internally called branches). Not ready, not soon.

  • Launchpad submissions being audited

    First batch surfacing ~next week.

The evidence board

Exhibits entered into evidence

7 exhibits were walked through during the session.

The interview log

Every question, on the record

42 statements logged. Search the file or pull a divider to narrow it.

Showing 42 of 42 statements

The screening room

Roll the evidence reel

The complete session, projected exactly as it was filed.

Conclusions

Findings, stamped and filed

  1. Debugging is one move: open Network, reproduce the issue, copy the error response, paste it into the builder.

  2. 4xx errors are yours to fix; 5xx are Base/provider issues. 403 = permission (RLS), 429 = rate limit.

  3. "Function not deployed"? Add a space in the code and Save & redeploy.

  4. Stuck app? Use the version-history clock to revert to any prior version.

  5. RLS = CRUD (Create/Read/Update/Delete) per entity — scan per-entity, not the global fix-all, and review what it applied.

  6. Every prompt invalidates your security — re-evaluate after each one once you're in production.

  7. To email yourself, your address must be in the app's users table.

Attached to the file

  • Office Hours archive app (all historical session/RLS VODs)
  • Amsterdam event Luma link (11 June)
  • Cookiebot (cookie-consent integration)
  • react-pdf (PDF rendering)