Skip to main content

Troubleshooting and FAQ

Common problems builders hit, with the usual fixes. If you are stuck after these checks, contact us.

Import mapping errors / import logs​

Symptoms: rows skipped, wrong columns, or a job that never finishes cleanly.

Try this:

  1. Confirm separator and encoding match the file (UTF-8 is safest).
  2. Enable Ignore the first row when the CSV has headers.
  3. Map every required field; empty required values fail the row.
  4. For Builder imports, open View import logs to see per-row errors while the job runs.
  5. On large imports, disable automatic fields, import, then re-enable and wait for recalculation.

See Importer widget (end users) and Builder import and export (admins).

E-mail is not sending​

Symptoms: tasks run but no message arrives; or messages land in spam.

Try this:

  1. Confirm Outgoing E-mail is enabled for this app (restored snapshots disable it on purpose).
  2. Open Outgoing E-mail → Pending messages and Recently sent (delivery logs) for queue errors or SMTP replies.
  3. Check the task condition — the action may be skipped when the condition does not match.
  4. Verify recipient placeholders resolve to a real address on the record.
  5. If you use a custom From domain on Bobuild’s server, update SPF (include:spf.bobuild.com) and ask us to enable the sender.
  6. If you use corporate SMTP, re-check host, port, TLS, and credentials.

For missing attachments, confirm the file field is filled on the record (or that related rows match the attachment filter) and that the file is not empty.

Auto field is not updating​

Symptoms: formula field stays blank or shows a stale value.

Try this:

  1. Confirm Automatic Value is enabled and at least one rule matches.
  2. Check whether Disable automatic fields is on under Settings → Advanced.
  3. If you just re-enabled auto fields, wait for the recalculation log to finish (or restart it).
  4. Verify referenced fields and relationships exist and filters in “count/sum of related” formulas are correct.
  5. Remember auto fields are read-only in the UI — editing them manually is not how they update.

See Auto fields.

Login or role rule not matching​

Symptoms: users cannot enter a portal, or the wrong people get in.

Try this:

  1. Confirm the portal uses the intended user object (e-mail + password fields present).
  2. Open login rules and compare them to actual field values on the user record (Active, roles, status).
  3. Multiple-choice roles must contain the exact tag the rule expects.
  4. After self-registration, users may need approval if your rule requires Active = true.
  5. Test in a private window to avoid a stale session from another portal.

See User login and Security overview.

Deployment did not promote what I expected​

Symptoms: production pages/tasks look unchanged, or data seemed to change.

Remember: deployments promote configuration only. Record data in the target app is never overwritten by a deploy.

Try this:

  1. Confirm you launched the deploy from the target (usually production) with the correct source app or snapshot.
  2. Read the deployment changes list — created / modified / deleted / deprecated.
  3. Compatibility failures block the run; fix them before retrying.
  4. Use the automatic pre-deploy snapshot of the target if you need a rollback path.

See Deployments and the Production playbook.

Document generation failed​

Symptoms: a Generate document task does not produce the file; the user may not see a clear error on the page.

What to do:

  1. Open Error Logs and look for Document generation (template, format, record, stage when available).
  2. Fix the template or task mapping, then run the task again.

See Using the template and Error Logs.

SQL command task failed​

Symptoms: a task with Run SQL command stops; later actions do not run.

Try this:

  1. Open Error Logs in the Builder sidebar and read the SQL command entry (message plus the statement).
  2. Paste the statement into the SQL Console and run it there to see the same validation errors.
  3. Use logical object and field names (tickets.status), not physical table names.
  4. Remember the command is not rolled back if a later task action fails — inspect data after a partial run.
  5. Check Repeat this action (once vs every record) and the task conditions.

See Run SQL command in a task.

Features that need enabling​

Some capabilities are gated and may require contacting Bobuild:

FeatureWhere documented
Scheduled tasksScheduled tasks
SPID / CIE loginUser login
Custom domains on CloudCustom domains
Custom From addresses on Bobuild SMTPOutgoing E-mail

Plan limits (number of apps, collaborators, and so on) also apply — restore of a snapshot can fail when you are at the app limit.

Widget or page not visible​

  • Check widget Visibility rules and page nesting.
  • Confirm the user passed login rules for that portal.
  • On menus, display rules can hide items per role — see Menu.

Still stuck?​