I confirm that it’s now working as expected, thanks.
Is the issue related to our account? Did it happen because of some configuration we did?
In short, is there something we should be aware of to avoid it in the future?
The bug was not specific to your account, it was specific to a license configuration and has been fixed. You don’t need to do anything on your side.