This seems to happen if I try to request the presence of a premium resource as a "resource". If I add the resource as an "optional attendee", the request will go through. This also seems to be related to my logging in AS the resource. When I first create a resource, everything seems to work from my user account, but once I log in as the resource to accept invitations and verify the schedule, future meeting requests sent from my user account which includ that resource give the error.
I cannot find anywhere to change the automatic accept/deny option while logged in as the premium resource. Additionally, I don't see why the system should throw this error... shouldnt the request be sent to the resource even if it is not set to auto-accept? Isn't the whole point of a premium resource so that someone can log in and manually accept the invitations?
Sorry if this is confusing, but it's been confusing me
