It would seem this was related to a performance problem with the Content Manager in general. (some tables didn’t load at all, after a time out and later we received general 500 error messages when visiting our sites).
After submitting a ticket, the problem disappeared as sudden as it appeared. Hopefully it won’t come back.