Error Code Reference
This page is the reference for the error and exception states you may see against an IZO™+ Multi Cloud Connect service in TCx, what each means, and what to do. The states that indicate a fault today are the two provisioning and termination exceptions, both of which Tata Communications recovers manually; the full numeric error-code catalogue is being compiled with the product team.
Status conditions that indicate an exception
|
Condition |
Meaning |
Recommended action |
|
Provisioning Failed |
Automated provisioning did not complete. |
No customer action needed. Tata Communications configures the service manually, after which it moves to Provisioned and then Active. |
|
Termination API Failure |
The termination automation did not complete. |
No customer action needed. The Tata Communications backend team terminates the connection manually, after which it reaches Terminated. |
These are exception states within the normal lifecycle, not dead ends. For the full set of normal states, see the Provisioning Order and Service Status Reference.
Reading a failure and getting help
When a service shows an exception state, note the Service Id and the time, and check whether it clears on its own (both exceptions above are recovered by Tata Communications). If it does not clear within the expected window, raise an incident from Support & Maintenance or from the service in Inventory, quoting the Service Id and the state.