Yes, this is worth an investigation to get it fixed. What would help is if you can reproduce the issue and tell us either the trace ID, if there is one, or when you executed the API and in what tenant so we can check the logs. You can submit your bug report to Bugs and I can forward it on to the appropriate team.