Hi @David Wrafter ,
I reached out to the owners of the incident and they said that the issue should be resolved now. Some people may have seen residual impact due to cached metadata, but a refresh was pushed so that issue should be resolved as well.
Could you try again and let me know if you are still receiving the same error?
If the issue is not yet resolved for you, let me know and we can sync over email for further troubleshooting.
Thanks,
Marilee
-
If this issue is resolved, please consider "marking as answer" so that others in the community searching the same error can more easily find the solution.