EFileReady/ Guides / Court Response of Failure

"Court Response of Failure": decoded

← All guides

Court Response of Failure is the automated rejection message from Tyler Technologies' e-filing platforms — eFileCA, eFileGA, eFileIL, eFileIN, eFileMD, eFileNV, eFileTX and eFileVA. It means the court's system hit a document format it cannot process. It does not tell you what is wrong, and the cause is almost always inside the PDF. Here are the documented culprits, with the fix for each.

The cause list

CauseDetailFix
Wrong page sizePages must be standard 8.5″ × 11″ letter; oversize pages trip processingRe-export or rescale to letter before filing
Unflattened fillable formsInteractive form fields are not processed; the system needs static contentFlatten the form (fields → static page content) before submitting
Incompatible creation softwarePDFs from Corel products — WordPerfect, PDF Fusion — are the documented offendersRe-create the PDF from Word or another mainstream generator, or print to PDF
Password protection / security restrictionsPassword-protected and permission-locked files cannot be processedRemove all security — see removing PDF security
PDF/A formatSupport guidance lists PDF/A among formats that can trip these portals — in practice usually a malformed PDF/A rather than a compliant oneVerify the file genuinely conforms (or re-export as ordinary PDF if your court doesn't require PDF/A) — see the state requirement guides for courts that do mandate PDF/A
Excessive scan resolutionOver 300 dpi creates files large enough to be rejectedRescan at 300 dpi, black-and-white or grayscale
Unintelligible imagesIllegible or landscape-oriented photos; systems expect portrait 8.5″ × 11″Rotate to portrait, 300 dpi, legible
Interactive elements & hyperlinksEmbedded URLs, local-file shortcuts and link annotations can cause processing errorsStrip interactive link elements before filing
Unsupported fontsSymbolic fonts — ZapfDingbats, Wingdings, Symbol — may not be recognizedUse standard text fonts; check local rules for accepted fonts

The PDF/A nuance

It surprises filers: some courts require PDF/A (Florida's portal is built around it; NY AD1 demands certified PDF/A) while Tyler-portal troubleshooting lists PDF/A as a rejection trigger. Both can be true — the difference is between compliant PDF/A and files that merely claim it. A converter's "PDF/A" label means nothing to a validator; the reliable path is to verify conformance before filing, whichever way your court leans. Our no-Acrobat guide covers free verification.

The fix workflow, under deadline

  1. Run the mechanical checks in order: encryption/passwords → page size → fonts → flattened forms → interactive elements → size.
  2. Fix everything found, re-export from the original source where possible (a re-export repairs more than an in-place patch).
  3. Re-verify — a second rejection costs another day of the clerk's 24–48 hour review window.
  4. Refile with the same envelope structure; check the rejection notice for anything procedural (fees, captions) you'd otherwise repeat.
A Court Response of Failure is a format problem, not a merits problem — and it never names the defect. Check everything mechanical at once instead of guessing one cause per retry: the checker on this site runs the PDF-side checks in seconds.
Check a PDF now
EFileReady — general information, not legal advice. Sources: Tyler-portal e-filing support documentation; court rules control. Illinois rejection standards · Password/security removal · All guides