BUG - Diabolic Servitude exiles creature that returns to battlefield with Persist before Diabolic Servitude trigger resolves to exile

Apologies for the lack of screen capture, it was a long game and we forgot to grab it.

Process of what happened:
-Creature with Persist exists on the battlefield, returned earlier with Diabolic Servitude
-Creature with Persist is sacrificed to an effect and goes to the graveyard (dies)
-Diabolic Servitude trigger and Persist trigger activate simultaneously
-Player chooses to resolve Persist trigger first
-After Persist trigger successfully resolves, Diabolic Servitude trigger resolves
-Diabolic Servitude incorrectly exiles the creature with Persist, despite M:tG rules stating that creature is a new object after leaving the graveyard zone

The Persist creature was either Kitchen Finks or Putrid Goblin, I can't remember which it was.

No source file or test is identified in the report. Start by reproducing the sequence with Kitchen Finks or Putrid Goblin, then trace the simultaneous Persist and Diabolic Servitude triggers. Done means the creature that returns from the graveyard is treated as a new object and is not exiled by the older Diabolic Servitude trigger.

Written by the indexing model from the issue text.