A similar problem occurred when testing the “Reports” add-on,
but a small change in the code was enough to fix it.
Regards