@LokeshC16778477 first ensure that both your rules and classes are updated to the same version across all environments to eliminate any version mismatches. Next verify that the user or service account has the necessary permissions to execute the pxcallconnector activity by checking role assignments and access controls. If permissions are correct, try clearing any server and client caches to remove outdated data that might be causing conflicts. If the problem persists, perform a clean redeployment by removing the existing problematic rules and classes entirely before redeploying the updated versions. If you still can’t delete the rules through the interface, consult your database administrator to carefully remove them directly from the database, making sure to back up your data first. Additionally, review your application and server logs for any detailed error messages that can provide more insight. Finally, consider reaching out to your platform’s support team if the issue remains unresolved. To prevent similar problems in the future, implement strict version control and automated tests to ensure consistency and catch issues early during deployments.