I created a test transaction in the Demo UI, but it doesn’t appear in the CMS Alerts section. Is the Demo UI still connected to CMS?

Yes, the Demo UI is still connected to CMS - this was a temporary issue affecting the Beta Sandbox on July 14, 2026. The dev team identified and fixed a bug where demo alerts were not being created in CMS; the fix was deployed and verified the same day. If you still don’t see your alert: (1) make sure you’ve refreshed your browser after a sandbox redeploy, since a new build was pushed and cached UI versions can appear stale; (2) note that the transaction ID shown on the debtor’s device in the Demo UI is the pacs.008 ID, while the alert in CMS is filed against the pacs.002 ID, so the two IDs won’t match - check the Demo UI console to find the pacs.002 ID used for the transaction submission and search on that instead. To reliably generate a test alert: Clear All (top right) → create a new debtor → create a new creditor → send a transaction (green) → send a second transaction (green) → send a third transaction that should trigger a flag (red/alert). The alert should then appear in the CMS Alerts tab (log in with a supervisor role to view it). Source: Tazama Head of Product & Tazama Product Owner, #tazama-public-beta, July 2026.

Update (July 15, 2026): At least one user (ThitsaWorks) reported that after following the reproduction steps above, the alert still did not appear in CMS - the Case Dashboard showed new low-priority cases (normal transactions) being created, but not the high-risk/alert case. This suggests the July 14 fix may not fully resolve the issue for all users. If you hit this after following the steps above, report it in #tazama-public-beta with screenshots so the team can continue investigating. Source: ThitsaWorks, #tazama-public-beta, July 2026.