Skip to main content

April 2026: Caddi now explains your runs — and fixes routine problems on its own

The headline this month: after every run, Caddi now tells you in plain language what actually happened and quietly fixes the routine problems it can handle itself. Plus loop versions, deeper Google and Outlook support, and a batch of fixes.

The headline this month: after every run, Caddi now tells you in plain language what actually happened and quietly fixes the routine problems it can handle itself. Plus loop versions (so you can edit a loop without breaking the one that's running), deeper Google and Outlook support, and a batch of fixes.

🚀 Caddi watches your runs, tells you what happened, and fixes routine problems for you

When a loop run didn't do quite what you expected, figuring out why used to mean digging through the whole run yourself. Now Caddi does that for you. The moment a run finishes, it analyzes what actually happened and gives you a clear, plain-language readout — which steps worked, what needs your attention, and why — so "what happened when I ran this?" is already answered.

It doesn't stop at explaining. When a run trips over something on Caddi's side — a transient or internal error rather than your process — Caddi can fix it on its own and hand you a corrected version to test, instead of leaving you to re-run blind. And by spotting patterns across your past runs, it suggests concrete improvements to your loop that you can review and accept.

The practical version: a filing loop that occasionally stumbled on a slow upload now gets flagged, fixed, and handed back to you as a tested version — and a loop you run every week starts surfacing the small change that would make it more reliable.

✨ New features

  • Edit a loop without breaking what's already running — loops now have versions. Make changes and test them as a new draft while your live version keeps running and stays on schedule, then publish when you're happy. No more choosing between improving a loop and keeping the one you depend on running.

  • Hand off loops when someone leaves — when you remove or suspend a teammate who owns loops, reassign those loops to someone else in the same step, so nothing they built goes dark when they're gone.

🔌 New tools & actions

  • Google Calendar & Google Docs, end to end — loops can now manage your calendar (create, update, move, and delete events, check who's free across calendars, even create an event from plain text like "client call next Tuesday at 3") and work in Google Docs (create, read, append or insert text, and find-and-replace).

  • Shared mailboxes in Outlook — loops can act on shared and team mailboxes, not just your own inbox — read, search, move, and reply from there.

  • Duplicate files in OneDrive — copy a file in place, with automatic naming so you don't get collisions.

  • Text-message signing reminders — signature requests sent through your loops can nudge signers by SMS, not just email.

  • Signed-document packs — when a signature request completes, a loop can pull everything back the way you want it: one combined PDF, each document zipped separately, or just the completion certificate.

  • Smarter NetDocuments filing — loops resolve the right workspace folder from a client and matter, so steps that file into NetDocuments need far less manual path setup.

🔧 Improved

  • PDF merging — when you merge PDFs, you can now flatten form fields so the result is a clean, final document instead of one with still-editable fields.

  • Clearer screen recordings — the step-by-step documentation Caddi captures highlights exactly where each click landed and frames each screenshot more cleanly, so recordings are easier to follow.

  • Knowing whose loop you're looking at — in shared workspaces, a loop you don't own now shows the owner's name in the header, so it's obvious when you're viewing a teammate's loop.

🐛 Fixed

We squashed a batch of bugs this month, including screen recordings cutting off before the end, large PDF data extractions returning truncated or malformed results, Trello card steps failing to read checklist states, and run status not displaying correctly for steps nested inside batches and conditions.

Did this answer your question?