I'm trying to figure out a blocking problem that arises when using Official Cisco APIs to interact with the CCX (v.10.6).
Sometimes I do a series of normal operations w/ the APIs that results in what I assume is an inconsistent state of the Outbound General Configuration. Moreover, this error is not systematic, so it is not easy to replicate in order to look into that. It just... "happens", and it blocks every interaction with the CCX via APIs.
This is an example of operations that sometimes trigger the error.
- DELETE https://<server>/adminapi/resourceGroup/<rg_id> (delete a resource group)
- DELETE https://<server>/adminapi/resourceGroup/<csq_id> (delete the csq such a resource group (<rg_id>) was associated to)
- DELETE https://<server>/adminapi/campaign/<campaign_id> (delete the campaign such a csq <csq_id> was associated to)
After those operations, If I query:
- GET https://<server>/adminapi/generalobconfig
I get this error:
{
"apiError": [
{
"errorData": "<csq_id>",
"errorMessage": "No entity found for query",
"errorType": "InstanceNotFound"
}
]
}
Looks like the csq <csq_id> is still listed in the assignedCSQs of the Outbound General Configuration (i.e., the generalobconfig), even if it has just been deleted.
To fix this, I have to log in to the CCX Web interface, go to Subsystems > Outbound > General, then I have to press on Update and all works fine again.
I have 2 questions about it:
- Why is this happening and how can I avoid this? As you may imagine, you cannot safety rely on APIs if you cannot figure this problem out
- Is there a way to fix this without a manual intervention?
Thanx
