We've resolved this. Thanks for posting! If you continue to experience this, please respond to this thread.
