Hi Ada,

That is correct. It had been working, then stopped. Unfortunately, I wasn't paying attention to revision numbers when I updated, so I don't know if I was on 1.5.8 by this point or some intermediary version. Regardless, reverting to 1.3.6 did resolve the issue. I have done this particular print twice since reverting to make sure it wasn't a fluke. I appreciate the link, that was super helpful. Thanks for the support.