Use “Repair blank checklist lines” in Recued. Remove the empty checklist lines a defect wrote before 21 September 2026, so a request opened with no documents stops showing a line whose label is a leftover placeholder. It asks before each removal, and it never deletes the request itself.
Repair blank checklist lines
Use “Repair blank checklist lines” in Recued. Remove the empty checklist lines a defect wrote before 21 September 2026, so a request opened with no documents stops showing a line whose label is a leftover placeholder. It asks before each removal, and it never deletes the request itself.
Complete workflow
Use Client Document Intake in Recued for drop link, reception, documents, and checklist. It includes 14 built-in actions and 8 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Open a document request” in Recued. Open one document request against a Reception drop link and write its checklist.
Use “Match a dropped document” in Recued. Fires when a file lands in the relevant record and proposes which outstanding checklist line it satisfies. It proposes only — the line stays missing until you confirm it.
Use “Confirm a document” in Recued. Accept the proposal on one checklist line, or clear it. This is the step that turns a file arriving into a document received — the two are different facts and the pack keeps them apart.
Use “Accept documents in bulk” in Recued. Tick the proposals you believe and accept them in one go. Same decision as confirming one line, made once for several — the board stays the board, and this is where a batch is done.
Use “Document requests board” in Recued. Every open document request with what is still outstanding, and every line waiting on your decision. It reads information without changing data in the connected service.
Show all 9 recipes
Use “Chase the missing documents” in Recued. Email one client the list of documents still outstanding, with their drop link.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “One required doc” in Recued. Open one required doc from the list that names it, and read everything recorded about that required doc on one page.
What this repairs, and why it exists
Until 2026-09-21, open-document-request mapped a bare {{item}} over its split label list, and that reference did not resolve in a map expression. Two things followed:
- a request opened with no documents at all still produced one checklist line, because the unresolved text counted as a label and satisfied the recipe's own
has_labelsguard; - that line was written into Records with the literal characters
{{item}}as its label, where the matcher then classified against it.
The resolver is fixed, so no new ones appear. This removes the ones already stored.
⚠ It deletes the LINE, never the REQUEST. A request with no lines is a request for nothing — but its drop link may already be with a client, so what to do about it is yours. The summary lists every request left empty; re-open it with real documents, or delete it yourself.
⛔ Deleting a record is destructive, so Recued asks you PER LINE. That is the engine's rule and a repair does not soften it: you will confirm each one, and you should read each label before you do — if a line says anything other than {{item}}, this recipe should not have found it.
⚠ Safe to run when there is nothing to repair: it reports zero and stops.
It needs FULL access at install
⛔ This repair is DENIED if the pack was installed with write access — pick all. It deletes (required_doc.delete), and deleting is classed destructive, which write does not grant.
⚠ The refusal is operation_not_granted at the gateway, before the first step runs — so nothing here can catch it and explain. That is why it is written where someone chooses the scope.
⚠ If you would rather not widen the scope for a one-off tidy-up, leave the lines: they are inert text on a request that has no documents, and nothing reads them except the board.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
limit
setting
=
25
Uses (2 operations)
recued-core.client-document-intake.required_doc.search
recued-core.client-document-intake.required_doc.delete
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.