Disallow Saving Botflows to RPA Central Once Contractual Max Hit

If 20 Botflows are contractually allowed to be saved to RPA Central, it would be extremely helpful if an error message appeared when trying to save Botflow number 21 that stated no more are allowed and disallow the user from saving to RPA Central. The user should still be able to save the Botflow locally, but not to RPA Central in this case.
Per conversations with support, there is no current mechanism in place to prevent contractual breach for the number of Botflows allowed. We have to manually delete added Botflows every 1-2 days in order to not breach our contract.