I actually believe this will need to be addressed on the tower-cli side as a stop-gap measure, only because it is vastly easier than the alternatives. I have one test in the AWX collection which is marked as xfail right now for this bug. I have some prior attempts at the problem lying around, but we updated the error handling to rase 400 errors in this case. You’re seeing that message. This is better than silently failing to copy the credentials in my book. This also gives some more options to catch and detect the error in tower-cli and make decisions based on that. I’m am still unsure of exact details of the solution right now, but it’s a known issue and a fix is planned for the sake of both the functionality of the AWX collection and send/receive.