Based on my assessments, apparently it is not sorting that was causing the issue but having duplicate beneficiary possibly returned in videoMetadata as we do also inject one default beneficiary manually as well.
Moreover my forced duplication test also produced expected error based on my assessment above. message only talks about sorting order and not pointing toward duplication, which is the issue with my test case.
Updated makeOptions method to discard any duplicated beneficiary along with sorting them out.
Also, this PR handle the passing of already extracted beneficiaries to schedule post routing.
What does this PR?
Based on my assessments, apparently it is not sorting that was causing the issue but having duplicate beneficiary possibly returned in videoMetadata as we do also inject one default beneficiary manually as well.
Moreover my forced duplication test also produced expected error based on my assessment above. message only talks about sorting order and not pointing toward duplication, which is the issue with my test case.
Updated makeOptions method to discard any duplicated beneficiary along with sorting them out. Also, this PR handle the passing of already extracted beneficiaries to schedule post routing.
Issue number
https://discord.com/channels/@me/920267778190086205/1277127392997146665
Screenshots/Video
Successful publishing of same draft that was failing with existing code.