Expiry Datetime incorrect for Tumbling Window Trigger Catchup Run?

Question

I have a pipeline that primarily has 2 copy activities . The sink for the copy activities is ADLS Gen 1, so it also sets an expiry datetime for each of the files copied over. It uses a tumbling window trigger with a self-dependency. Recently, the pipeline failed, and in the catchup runs the expiry datetime that I'd set wasn't used and instead the default was used. Is there any reason why this would happen and how I could fix it?