Thanks. I did update the story to reflect the apparent fix. I'm still trying to verify if this behavior remains in some form.