User Creation Failures
Access Prerequisites
- Permission (module):
digitalAccountErrors - License/Feature: None
- Menu container: GENERAL → group Audit
What it is / when to use
The User Creation Failures screen (/customer-creation-errors) lists the customer creation attempts (in CPM — Customer Profile Management) that failed, storing the error message and the original request that triggered the attempt.
Use this screen to diagnose why a user registration was not completed (validation, duplicate, integration) and, after addressing the issue, dismiss (remove from the pending queue) the record.
Prerequisites
- Permission: module
digitalAccountErrors(shared with the digital bank creation failures screen). Permission is dual — CPM enum on the backend + dynamic module in the DB. - License/Feature: none.
- Dependencies on other screens: records come from the same creation audit chain (CPM), which persists the request even when the operation fails.
Step by step
- Access the menu GENERAL → Audit → User Creation Failures.
- The table loads paginated records (10/25/50/100 per page).
- Click on a row to expand and see the full
request(JSON) and the detailed error message. - After addressing the case, click Dismiss to settle the record.
Filters and columns
| Filter / Column | What it shows | Data source |
|---|---|---|
| Error (summary) | First line of the error message, truncated at ~140 characters | error (summarised by summarizeError) |
| Request fields | Values extracted from the original request (e.g. email/document) | request[...] via extractField |
| Date | Timestamp of the attempt | createTimeStamp |
| Action: expand | Shows the request formatted as JSON | request (via formatPayload) |
| Action: dismiss | Removes the record from the pending queue | dismiss(id) |
Actions and modals
- Expand/collapse (click on the row): toggles the display of the full request payload and error message.
- Dismiss: asks for confirmation (
confirm) and calls the backend (DELETE) to remove the record. On success, displays feedback and reloads the list. - Refresh: reloads the records.
Business rules / caveats
Attention
- Dismissing is final for the pending queue: the record stops appearing. Confirm that the case was effectively addressed (or is a false positive) before dismissing.
- The
requestmay contain PII (name, document, email). Handle in accordance with LGPD.
- Difference from "Digital Bank Creation Failures": here the focus is on customer/user creation (CPM); the other screen deals with bank account opening at the BaaS provider. A registration may succeed in CPM and fail at the digital bank (or vice versa).