Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

The internal tool my team uses in Retool or Appsmith is broken

Short answer

Low-code internal tools usually break for ordinary reasons: a data source credential expired, an API or database changed, a query was edited in place, or the person who built it left. Check what changed, work out who owns the workspace, and make a backup before anyone edits the live app.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A button or table in the tool shows an error or loads nothing.
  • The person who built it left and nobody else can edit it.
  • A change fixed one page and broke another.
  • The tool is slow because it loads too much data at once.
  • I do not know where the tool is hosted or who pays for it.

Why does this happen?

  1. A connection behind the tool changed

    The database password, API key or token that the tool uses was rotated, expired or revoked. The app itself did not change, but every query using that connection fails.

  2. The source system changed

    A column was renamed, a service changed its API or a database was moved. Queries in the tool still point at the old shape.

  3. Edits happen in the live app

    Both platforms document version control for tracking changes. Appsmith documents Git-based version control with branches and rollbacks, and Retool documents source control as a feature. If it was never set up, edits go straight to the version your team uses.

  4. Hosting is unclear

    Retool lists two options, Retool-hosted and self-hosted. Appsmith can be used on its cloud or installed on a private server. A self-hosted copy needs updates and backups that nobody may be doing.

  5. It grew beyond its first purpose

    A quick tool that began with one table now runs approvals and sends emails. Logic hidden in many small queries is hard to follow, and the tool gets slow.

What can I do about it today?

  1. Find who owns the workspaceLook in the platform's admin or member list for an owner. If the owner has left, find who pays for the plan or hosts the server.
  2. Screenshot the errorNote which page, which button and what time. Do not click repeatedly, because some actions write data.
  3. Do not edit the live appAsk your tool to duplicate it, or wait until a copy exists.
  4. Ask what changed recentlyA password change, a new field, a plan or hosting change. Most failures follow one.
  5. Write down what the team uses the tool forThe three most important actions. That is what must work first.

When should I bring someone in?

  • The tool changes orders, payments or customer records.
  • Nobody has admin access or knows where it runs.
  • The tool needs more than low-code can reasonably carry.

How do I handle it?

  1. Get access properlyI ask for a named admin account, not a shared password, and note who owns hosting and billing.
  2. Duplicate before changingI work on a copy, and use version control where the platform supports it.
  3. Trace the failing queryI follow the failing query to its source: credential, API change, renamed column or bad input.
  4. Decide whether to keep or replaceSmall tools stay where they are. If logic and data volume have outgrown it, I propose a custom screen over the same database.
  5. Leave a written handoverWhat the tool connects to, who owns each credential and how to recover it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can the tool be rebuilt as normal code?

Yes. Once the data and rules are written down, a custom web app can do the same job without the platform limits. It is worth it only if the tool has outgrown low-code.

Will I lose the tool if the builder left?

Not usually. The workspace belongs to whoever holds the account. The risk is that nobody has access, so check that first.

Is a self-hosted version safer?

It gives more control, but it also means someone must update and back it up.

Do I need version control for a small tool?

It helps most when more than one person edits. It lets you undo a bad change.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.