KamoCRM

Offer Finish setup on a KamoPBX server that was never provisioned

Fixkamo-internal
Shipped
27 ஆகஸ்ட், 2026 அன்று 6:52 PM UTC
Author
kamo
Commit
8b1ddbb

The card told the admin their phone system was "still being set up" and to wait. That was never going to clear: KamoPBX provisioning runs synchronously when the server is created, so a server without an account has already failed, and until now nothing could retry it. An org sat on that message with a dead server and the misleading "Phone provider instance not found" underneath it. Uses the renamed kamoPbxNotProvisioned copy — it says what actually happened — and adds a Finish setup button wired to the new POST /{id}/provision, which is idempotent, so pressing it on a healthy server does nothing. Dictionary pushed first (kamo-translation-dictionary 99a90d7a): CI clones it unpinned at build time, so a consumer commit referencing a new key is only buildable once the key is on its default branch. Verified against a fresh clone rather than the local messages/ copy, which is gitignored and stale.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing