@Jose Angel Martinez Sanchez Thanks for reaching out. There was an interment issue where only a few requests were resulting in Internal/server error on the scale unit where your standard service bus namespace is deployed.
In other scenarios such as service updates on the scale unit where the namespace is hosted then you may see these errors during that time. These updates are pushed by the product group from time to time to improve the service.
There will be no notification sent to the customers for these service updates but to minimize the impact in your application please make sure that retry logic is handled in the code with exponential back-off so that intermittent issues/service updates like this should not affect your workflow: https://learn.microsoft.com/en-us/azure/architecture/best-practices/retry-service-specific#service-bus-retry-guidelines
We also recommend you create Service Bus partitioned entities, in cases wherein there are issues with the service bus infra or upgrade, it helps avoid having a single point of failure.