If there is a way I can access the error log to provide more details on this error, please let me know how to do so and I will attach it to this issue.

Thanks!

This actually appears in other cases as well, I am noticing

fixed in 10.0.5