Mighty Network Member Badges and Photos Now Stay in Sync

Fixed

Mighty Network Member Badges and Photos Now Stay in Sync

Case badges and photos now update as soon as someone joins or leaves your Mighty Network.

What was happening

Before

Case badges and photos didn’t stay in sync with Mighty Network membership when people joined or left.

Now

Doobert updates cases in real time whenever someone joins or leaves the Mighty Network.

What’s fixed

  • When someone joins. Cases that share the new member’s email address are automatically linked to their Mighty Network membership, so those cases show the member’s badge and photo. This includes cases that were previously marked as “Not a Member.”
  • When someone leaves. Their badges are removed from the linked cases right away.

Why it matters

A case’s member badge always reflects whether that person is currently in your Mighty Network, so you can trust what you see on the case.

No More Duplicate Texts From a Case’s Communication Tab

Fixed

No More Duplicate Texts From a Case’s Communication Tab

Clicking Send once on a case’s Communication tab now sends exactly one text message.

What was happening

Before

Sending a text from a case’s Communication tab could send two identical texts to the contact, even when Send was clicked only once. The case log showed two entries.

Texts sent from the chat drawer (the text-message inbox) were not affected.

Now

One click sends one text, and the case log shows one entry.

The Send button locks as soon as you click it, so a quick double-click doesn’t send a second message.

What’s fixed

  • One click, one text. Sending a text from a case’s Communication tab sends it once, including when Undo Send is turned on.
  • Double-clicks are covered. A fast double-click on Send still sends only one text.
  • Pressing Enter is covered too. Submitting with the Enter key sends only one text.
  • Emails are protected the same way. A fast double-click on Send for an email from the Communication tab now sends one email.
  • Other case tabs run actions once. The same fix applies to the Overview, Tasks, Scheduling, and Workflow tabs, so actions there happen only once.

Why it matters

Your contacts get each message once, and your case logs stay accurate.

See it in action

  1. Open any case, go to the Communication tab, and send one text. The case log shows one entry, and the contact receives one text.
  2. Double-click Send on another text. Only one text is sent.
  3. Send an email from the same tab. Only one email is sent.

Workflows No Longer Get Stuck on “Running”

Fixed

Workflows No Longer Get Stuck on “Running”

Automated case workflows now finish, fail with a clear reason, or keep moving as built, instead of sitting on “Running” with nothing happening.

What was happening

Before

Some automated case workflows, such as reminder emails, texts, and follow-ups, could get stuck on “Running.” They never completed and never sent their next step.

When a step failed, for example because of an invalid email address, no error appeared, so the case looked active even though nothing else would happen.

Now

When a step can’t finish, the workflow ends cleanly instead of staying on “Running.”

A genuine failure shows as Failed on the case’s Workflow tab with a plain-English reason, such as an invalid recipient email address.

What’s fixed

  • No more stuck workflows. If a text or email won’t send, the case is missing or archived, or a step errors out, the workflow ends instead of staying on “Running.”
  • Failures explain themselves. Failed steps show as Failed on the Workflow tab, along with the reason.
  • Replies move workflows forward. Replying to a workflow email or text advances the workflow through any time delay to the next step. Replying more than once advances it only once.
  • Long delays fire on time. Delays set weeks out are scheduled and run when they’re due.
  • Saving keeps steps in place. Opening and saving a workflow no longer moves steps around, so a workflow continues after a Time Delay exactly as built.
  • Stopped workflows can be re-run. After you stop a running workflow, you can execute it again on the same case. This was previously blocked with a “Workflow is running with cases…” error.
  • Archived and deleted cases stop their workflows. When you archive, delete, or transfer a case, its running workflows stop and nothing further is sent.
  • No false error after a reply. When a workflow ends after a reply with no further steps, the Workflow tab shows “Workflow ended.” and Completed. The red “step type ‘yes’ is not supported” message no longer appears.

Why it matters

Your reminders and follow-ups no longer stop silently. Every workflow now reaches a clear outcome you can see on the case.