Thanks for your post.
We were able to get around the issue while it’s still outstanding by moving to a larger sized AWS instance with more memory. I hope that helps you until the bug is fixed.
Thanks for your post.
We were able to get around the issue while it’s still outstanding by moving to a larger sized AWS instance with more memory. I hope that helps you until the bug is fixed.