Workflow Automation & Responsible AI

A scheduled notice may still go out after a deadline has been extended if the workflow uses an earlier snapshot or queued message. Recipients may then act on obsolete dates. What to check Compare deadline change history, queue time, workflow execution state, message template variables, and cancellation behavior. Test an extension made after a...

A survey may be sent when a ticket is closed automatically even though follow-up work remains or the customer’s issue has reopened. Timing can skew feedback and frustrate customers. What to check Check survey trigger conditions, current case state, reopen events, delayed integrations, and survey queue. Test cases that reopen before and after the survey...

A reminder may remain queued after a request is cancelled, because the workflow captured the earlier state or cancellation does not remove scheduled messages. The recipient may think the request is still active. What to check Inspect cancellation events, reminder queue, current record status at send time, retry logic, and integration delays. Test a...

A workflow may send an invoice notice twice after a retry, a status update, or a manual resend. Customers may pay twice or contact support because the messages look like separate invoices. What to check Compare invoice IDs, send logs, event IDs, retries, provider delivery receipts, and whether each trigger creates a new message record. Check concurrent...

A workflow may use an outdated contact field, duplicate account, or prior owner when sending a notification. The message can disclose information or confuse a customer. What to check Trace contact source, record ownership, merge history, consent, event timing, and notification preview. Test records with changed contacts and multiple linked accounts....

Duplicate notices can result from retries, repeated triggers, parallel workers, or a missing completion check. Customers may receive multiple messages even if the underlying task ran only once. What to check Trace trigger IDs, retry history, workflow state, queue delivery, and message-provider logs. Determine whether duplicate sends share the same...

An approval workflow can continue applying an old rule if policy text is copied into the automation or if updates do not reach the decision step. What to check Identify where policy rules live, who approves changes, how versions are deployed, and which in-flight requests use the old version. Test a known changed rule in a safe environment. Recommended...

A pause control can prevent an automation from continuing during an incident, but an unclear control may stop unrelated workflows or leave queued work in an unknown state. What to check Define who can pause, which jobs are affected, what happens to in-flight items, how resumption is approved, and how activity is logged. Test the control in a...