SurgeTK Release Notes - September 13, 2026

This release is about work that finishes on its own. A surge now completes even when the connection to your browser is lost partway. A Zoho sync updates only the withdrawals it reads and leaves the rest of the account alone. And a Redtail contact with an empty name no longer stops a sync partway.

Everything below is live for every firm and happens on its own. Nothing here asks you to turn something on.
​

Surge runs

A surge finishes even when your browser tab or the web server loses the connection during the run.

• A run no longer depends on the tab that started it. A surge run is now recorded in SurgeTK from the moment it starts, with one entry per household. The packets build in the background as before, and the run is closed by that same background process when the last packet lands. Closing a tab, a dropped connection, or a routine server restart during a long batch no longer leaves the run open.
• A run that goes quiet is closed for you. If a run stops making progress for ten minutes, SurgeTK checks each household that has not finished. A household whose packet is already built is counted as done, a household whose job is still queued is left to run, and the batch closes with its ZIP once nothing is outstanding. A run cannot stay on the progress screen indefinitely.
• The ZIP and the run report describe the same households. Every household that produced a packet is included in the ZIP and counted in the run summary, including a household the report lists with an issue. The households listed as included and the households listed with issues now add up to the run.
• Run history shows what is in progress. The run history table and the run report now show a run that is still running, and the households in it that have not started yet.
• A run without an archive says so. If the ZIP could not be created, the completion message tells you the archive is missing instead of reporting a download, and the run detail opens so you can see each household's result.
• Every run logs its completion. The activity log now records a Surge run completed entry for every run that recorded a start.

Zoho systematic withdrawals

A sync updates the withdrawals it reads and leaves the rest of the account alone. This section applies to firms that sync Distribution records from Zoho.

• Each withdrawal is matched to its Zoho record. When a sync reads a changed Distribution record, it updates that one withdrawal on the account in place. The other withdrawals on the account are not touched by that run.
• Withdrawals you entered in SurgeTK stay. A withdrawal with no Zoho record is yours, and a sync never removes it. If Zoho later sends a record with the same amount, frequency and withholding, the two are treated as one withdrawal rather than shown twice.
• A withdrawal leaves an account only when Zoho confirms it. A withdrawal is removed only when a complete read of Zoho shows the record is gone, or now belongs to a different account. A record the run could not read in full is kept for you to review rather than removed. A record moved to a different account in Zoho can stay listed on its old account until the next Deep sync.
• Editing or importing an account keeps the Zoho link. Saving an account from the account window, or importing accounts from a spreadsheet, now keeps the link between each withdrawal and its Zoho record, so the next sync updates those withdrawals in place instead of adding a second copy. An imported row that matches a Zoho withdrawal exactly is not added twice.
• What to check on an account. Guardrails, Buckets and Homework read the withdrawals listed on the account. If an account shows the same withdrawal twice, delete the copy that did not come from Zoho; the sync will not add it back. If a withdrawal is missing, add it in Zoho and run a sync, or add it in SurgeTK.

Redtail contacts

A contact with an empty name no longer stops a sync partway.

• An empty first or last name gets a placeholder. A Redtail contact whose first name or last name is blank, which is common when a trust or a business is entered as an individual contact, now syncs with (Unknown) in the empty half. The sync completes, and the contact's household and accounts sync with it. A contact with both halves blank keeps the name Unknown Client as before.
• Enter the name in Redtail and it flows through. The next sync replaces the placeholder with the name you entered. There is nothing to change in SurgeTK.
• The sync shows the contacts to fix. The sync history drawer has a new Name placeholders card listing each contact that received a placeholder, with its Redtail id. The sync report carries the same list.
• Contacts already affected correct themselves. A contact that received a placeholder before this release, or whose sync ended partway because of an empty name, is repaired on the next sync. There is nothing to click.

Redtail sync

Your status filter now decides who is in a household, and a full re-read is one checkbox away.

• Skipped statuses now apply to family members too. When the sync imports a client, it also imports the contacts in that client's Redtail family, so a spouse who carries a non-client category still lands in the household. Those family members now respect the statuses you skip. Add Child of Client, Grandchild of Client, or whichever status your firm uses for adult children to the skipped list, and they stay out of their parents' household. The note under Contact Statuses in the filter window explains this. A family member already in SurgeTK stays until you remove them.
• A list of statuses to import is not applied to family members. If your filter names the statuses to include rather than the ones to skip, a spouse whose status is Spouse of Client still comes in with the client. Only a skip list changes who joins a household.
• Re-read every contact. The sync window has a new checkbox, Re-read every contact. A normal sync asks Redtail only for the contacts that changed since your last sync. Tick the box to read all of them: slower, but it applies your current filters to every contact. You no longer need to disconnect and reconnect Redtail to do this, and your saved filters stay in place. The box is unticked each time the window opens, so a full re-read is a one-time choice.
• A full re-read can bring a household back. It reads every contact that matches your filters, including contacts behind a household you removed in SurgeTK. Before you tick the box, exclude those contacts in Redtail or skip their status in your filters.
• Saving a filter tells you when a full re-read is needed. When you save a change to your Redtail filters, SurgeTK reminds you that filters apply to the contacts your next sync reads, and points you at the checkbox. Saving a filter never starts a sync on its own.
• A retired Redtail value stays in your filter. A category or status you selected that Redtail has since renamed or removed still shows in the filter window, marked (no longer in Redtail), and stays saved until you untick it. If Redtail cannot be reached while the window is open, your saved selections are kept as they are.

Value-Add PDFs

Every PDF is checked before it is saved or sent.

• A PDF is checked for its content before it leaves SurgeTK. A Value Add, a Quick Preview and each page of a surge packet are now checked for a rendered Value Add before the PDF is saved, downloaded or emailed. A page that did not render as a Value Add is reported in the run instead of being kept as a PDF. In a surge packet, the packet ships without that page and the household is listed with an issue.