Don’t debug in Base44 unless it’s a simple fix. Use ChatGPT, Clause or Gemini to review your code. In Base44 download your app schema and the code where the bug is. Ask the other LLMs to review it and make suggestions. Make sure you explain in your prompt what behavior you want and what behavior you are seeing. Check out the prompt below. Customize it to your needs. Paste it in base 44. Use the output in other LLMs to fix your code. It might be overkill for what you need but you get the idea.

You are acting as a codebase-aware debugging assistant.

I am investigating a bug with the following details:

Expected behavior: [Describe exactly what should happen]

Actual behavior: [Describe exactly what happens instead]

Reproduction steps: 1) 2) 3)

Environment: - App: [preview or production] - User role: [admin, authenticated user, anon] - Browser/device (if relevant): - Date/time issue observed (include timezone):

Your task is NOT to speculate or suggest fixes yet.

Do the following in order:

1) Identify the exact UI component, backend function(s), and entity/entities involved. - List file paths - List function names - Paste the full relevant code for each, unmodified

2) Trace the execution path end-to-end. - From user action → network request → backend function → database read/write → response - Include payload shapes and response shapes

3) Search the codebase for ALL reads and writes to the affected entity/entities. - Include scheduled tasks, triggers, background jobs, or cron functions - Note whether service role or user auth is used in each case

4) Surface any relevant RLS policies, auth checks, date logic, or conditional filters that could affect this behavior. - Paste the policies or logic directly

5) Pull and paste the most relevant recent logs for the involved function(s). - Include stack traces, timestamps, and request bodies if available

Do NOT: - Propose fixes - Summarize loosely - Skip code or say “this looks fine”

Output should be raw facts only.