We have a bug open on this, but are having trouble reproducing in our environment to fix. We're continuing to investigate.
Also, just to be sure, you've upgraded to the latest release (1.0.1) and still see this?
We have a bug open on this, but are having trouble reproducing in our environment to fix. We're continuing to investigate.
Also, just to be sure, you've upgraded to the latest release (1.0.1) and still see this?