Troubleshooting

How to use this docs page

This page is meant to answer one operational stage of the DullyPDF workflow well enough that you can run a controlled test without guessing. Read the sections below, validate the behavior against one representative document, and only then move to the next linked page.

That order matters because most setup failures come from mixing detection, mapping, fill validation, and sharing into one unstructured pass. A narrower review loop keeps troubleshooting faster and makes the template easier to trust once you save it for reuse.

Troubleshoot by stage

1. Upload: confirm the file is a real PDF, under 50MB, and not encrypted.
2. Detect: review low-confidence items and obvious false positives before moving on.
3. Rename or map: confirm the schema is loaded, credits are available, and checkbox or radio metadata still make sense.
4. Fill: clear the output, refill from one representative record, and inspect the risky fields first.
5. Publish: confirm you are working from the intended saved template or group snapshot before sharing a link or API endpoint.

Detection issues

• Re-upload cleaner PDFs when labels are faint or skewed.
• Use inspector tools to correct false positives and missed areas.
• Confirm document is not password protected.
• If upload fails immediately, confirm file type is PDF and size is under 50MB.

Rename and mapping issues

• Check that schema headers are loaded before mapping.
• Retry with Rename + Map when direct mapping misses ambiguous names.
• Review low-confidence rename outputs before filling.
• If blocked, confirm credits and role on Profile. The server enforces bucketed pricing and returns remaining/required credits in errors.

Fill output issues

• Ensure identifier key matches the data source column you are searching.
• Confirm checkbox options align with mapping/group metadata.
• If values look stale, clear values and refill after mapping edits.
• For missing checkbox fills, inspect rule operation (`yes_no|presence|enum|list`) and valueMap normalization.

Common validation and runtime messages

• `Choose a CSV, SQL, Excel, or JSON source first.`
• `No record rows are available to search.`
• `Enter a search value.`
• `Choose a column to search.`
• `OpenAI credits exhausted (remaining=X, required=Y)`
• `Upload a schema file before running mapping.`
• `Template session is not ready yet. Try again in a moment.`

What to capture before support

• The exact route or page you were on when the issue happened.
• The action order that led to the failure: upload, detect, rename, map, fill, publish, or sign.
• One screenshot that shows the state of the template or error message clearly.
• The exact validation or runtime message if one was shown.

Support

For persistent issues, include your route, action sequence, and screenshot evidence when contacting support at justin@dullypdf.com.