Unable to add new Client API ID to partner billing rule

Products

• CloudHealth

Issue/Introduction

When trying to add a new Client API ID to your partner billing rule you might see a 500 internal server error using our CloudHealth API. If you're using our CloudHealth UI with the Network tab open in developer tools you might see a 422 unprocessable entity error message. 

Error message from CloudHealth API

Error message from CloudHealth UI

Resolution

These errors might be occurring, because there is a Client API ID in your billing rule that is no longer valid due to the customer migrating to be under a new partner tenant. The solution is to open a support ticket so Engineering can determine which Client API ID is invalid and remove it from your rule. Once the old invalid Client API ID is removed, you should then be able to add your new valid Client API ID for your new customer to your partner billing rule.