Self-Healing
When Self-Healing is on and someone on your team hits a bug — a crashed page, a failed action — CartonCrew reports it automatically so a fix can be proposed. You don’t have to file anything; the broken moment becomes the bug report.
Who this is for: org admins decide whether it’s on; every member benefits.
What it does (and doesn’t)
- On: errors your team encounters are captured automatically and sent to the CartonCrew team, deduplicated, and tracked through to a fix. You’ll see your organization’s reported incidents and their status right under the toggle.
- No personal data leaves your tenant. Reports are scrubbed before they’re stored: emails, phone numbers, and identifiers are masked, and form contents are reduced to field names — never values.
- Fixes are never automatic. Every proposed fix is reviewed by a person and goes through the normal release process. Because CartonCrew is one product serving many organizations, fixes reach everyone — turning Self-Healing off only stops the error reporting, not the fixes.
Steps
- Open Settings → About. The Self-Healing card sits under Submit feedback.
- An admin clicks Turn on (or Turn off — it’s off by default).
- That’s it. If something breaks while it’s on, you’ll see a friendly “reported automatically” message instead of a dead end, and the incident appears in the card’s list with a status: Reported → Being investigated → Fix proposed → Fixed in v1.x.
Common issues
- The incident list is empty — good news: nothing has broken since you turned it on.
- You turned it off but still got a fix — expected; fixes ship to every organization. The toggle only governs whether your errors are reported.
- Worried about sensitive data — the scrubbing happens before anything is stored, and what is kept is visible to you in the incident list. The sub-processors page covers who processes what.
Last updated: 2026-06-11 · Applies to: CartonCrew v1.121+