Yeah, I've seen that error too.
In my case, it was because I was trying to access a feature that required a higher subscription level.
In my case, it was because I was trying to access a feature that required a higher subscription level.
