Skip to main content

What's New - September 15th, 2026 Release

Editable reply subjects, a warning before losing unsaved edits, and dozens of fixes.

N
Written by Nick Laffey

Email

New: Reply subjects are now editable

When you reply to an email from a case, you can now change the subject line before sending. Previously it was fixed to "Re:

" and could not be edited. If you leave the subject as CK suggests, it still resolves to "Re:

" exactly as before — this includes acknowledgements Gustav sends automatically on your behalf, so nothing changes there.

If you do edit the subject, be aware that this starts a new conversation in the recipient's Outlook, since Outlook groups conversations by subject line. The message itself remains correctly linked to the original case and email thread in CK — only how it appears in the recipient's inbox changes.

Changed: Excluded emails no longer appear in the Emails screen

Emails CK excludes from processing no longer appear in the Emails screen. They stay in the mailbox, marked with the exclusion category.


Cases and ERP Tickets

New: A warning before you lose unsaved edits

Closing the action drawer for an email, ERP ticket, phone call, or work order — by clicking outside it, pressing Escape, or using the close button — used to discard any unsaved edits without warning. CK now asks first: Keep Editing returns you to your changes, and Close Without Saving discards them and closes the drawer. If your edits are already saved, the drawer closes as before, with no prompt.

Changed: A ticket deleted in D+ is now clearly marked and locked

When a case's linked ERP ticket has been deleted directly in D+, CK now shows "This ERP ticket no longer exists" instead of letting you keep working with it as if nothing had changed. Creating a work order, changing the ticket status, or filing an email against that ticket is disabled everywhere it could be attempted. The ERP-Ticket tab tells you to unlink it and link the case to a different ticket, or create a new one.


Bug Fixes

  • Sent emails no longer contain misplaced backslashes: A formatting quirk in the email editor could insert stray backslash characters into text and links before sending — for example, a file name like "kuendigung_stellplatz.pdf" could appear to the recipient as "kuendigung_stellplatz.pdf". This no longer happens.

  • A readable .msg attachment is no longer reported as corrupt: Some Outlook .msg attachments, particularly older ones, could be wrongly flagged as unreadable when CK tried to process them. These now convert correctly.

  • Long case descriptions can now be saved: A case description longer than roughly 2,700 characters previously failed to save, with the edit silently lost. There is no practical length limit now.

  • Unlinking and relinking an already-processed ERP ticket no longer leaves a case stuck: In a specific sequence of steps, a case could end up with no work order, no ERP ticket, and no way to add a replacement. Cases affected this way are being repaired, and new ones can no longer get into this state.

  • Re-linking an email to a case it is already documented against no longer duplicates the paperwork in D+: Attaching the same email to a case a second time could file the same documents into D+ more than once. CK now only files documentation that is actually new.

  • Occasional errors when adding an action to a case are fixed: Two actions created on a case at nearly the same moment could occasionally collide and fail with an error instead of both succeeding.

  • D+ ticket subjects no longer get an extra prefix on update: Updating an already-linked D+ ticket could add a duplicate ticket-number prefix to its subject line each time it was changed. The subject now updates cleanly.

  • An incoming email is no longer lost when it involves buildings under two different D+ accounts: In this specific situation, CK could fail to create a case for the email without retrying it. This is now handled correctly and no email is dropped.

  • The "Sent" column's sort indicator now shows correctly when the email-messages list loads: The list was already sorted newest-first by default, but no arrow appeared on the "Sent" column header until you clicked it. The indicator now appears from the start.

  • Restoring a dismissed email now shows the correct confirmation: Un-dismissing an email previously showed the same message as dismissing it, which could be confusing. It is now clear when an email has been restored.

  • Several untranslated and mistranslated labels in the German app are fixed: The confirmation dialog for unlinking an ERP ticket previously showed some English text, and "Sender" was mistranslated as "Versenden" (the verb "to send"). Both now show the correct German text.

  • Address search returns results much faster: Searching for a building by street address could take over a second and occasionally time out. It is now well under a tenth of a second for the same search.

  • Gustav could open a second case for an issue someone else had already reported: A search scoped only to the original sender could come back empty and be read as proof nothing existed, missing an open case already reported by someone else in the same building. Gustav now also checks for an existing case at the building level.

  • A reply to an email CK already held could still open a duplicate case: Gustav did not always recognise that an incoming reply continued an existing email thread, and could create a new case instead of continuing on the existing one. Thread continuation is now considered before a new case is created.

  • Gustav no longer appears to get stuck repeating the same search: In rare cases, Gustav could re-run the same lookup many times while preparing a single response, taking far longer than usual to answer. A limit now stops this from happening.

  • Gustav no longer creates a work order you did not ask for: If creating a D+ ticket was refused because a matching ticket already existed, Gustav could offer a work order instead, even though nobody asked for one. Gustav now only drafts a work order when you have explicitly requested or confirmed it, and otherwise reports the refusal and asks how you would like to proceed.

  • Gustav no longer claims to have made a change that did not happen: Asking Gustav to edit an action whose draft had already been completed could get a success message even though nothing changed. Gustav now tells you honestly that the action can no longer be edited.

  • An overly long Personal Instructions document no longer breaks every Gustav conversation: If your Personal Instructions for Gustav (under Gustav Settings) grew past the length limit, every message to Gustav could time out with no explanation. CK now refuses to save instructions over the limit, and shows a banner if a previously saved document has become too long, so Gustav keeps working without it until you shorten it.

  • Building-wide letters now reach every tenant, reliably: The recipient list for a letter addressed to everyone in a building could vary between attempts, occasionally leaving someone out. The recipient list is now complete and consistent every time.

  • Gustav no longer reports a D+ ticket number it made up: In rare cases, Gustav could state a ticket number that did not actually exist. Gustav now only reports ticket numbers that come directly from D+.

  • Gustav's answer no longer appears as a broken red error box: Certain formatting in Gustav's reply could cause it to fail to render, showing a technical error message instead of the actual answer. This no longer happens.


Related Articles

Did this answer your question?