@Herman, Justin Thank you for reaching out and for being patient while we resolved this issue.
The issue was resolved by opening a support ticket. The backend team updated the permissions on the affected resource.
Our product team is aware of this known issue caused by the latest deployment, and the upcoming releases will address this fix.
In the meantime, if you have any questions or concerns, please feel free to reach out. We are happy to help.
Thank you for accepting this answer as it will be useful for other community members with the same issue.
Regards,
Oury