This message was deleted.

I have figured this out - the issue was there was such a resource with the old name and it was aliased to the new name