In signing with the second social gathering, the multisig script that’s your witness script bought tousled.
In each the preliminary PSBT and the primary signing, we see that the witness script is
522102dbbedff721dcdc7737c0e931c0473db3aadf4690f01dd5fc6da65188e21ecffd2102f4e91f49be47c24571e100c501cc50e9c499e744a25e51e2153d26b85660595252ae
which is decoded as
2 02dbbedff721dcdc7737c0e931c0473db3aadf4690f01dd5fc6da65188e21ecffd 02f4e91f49be47c24571e100c501cc50e9c499e744a25e51e2153d26b856605952 2 OP_CHECKMULTISIG
This script has a sha256 of 4b29bdce823c1afde68cc26012e49a913fc005a629748afbea7285d7ac281b7c which matches the hash given within the redeem script of the enter, and the redeem script has a hash of 4d3a0d4465e19bb387df92f5e052f24370718117 which matches the hash within the output script of the output being spent. That is all appropriate.
However once we have a look at the ultimate transaction, the script for some cause is modified to
522102f4e91f49be47c24571e100c501cc50e9c499e744a25e51e2153d26b8566059522102dbbedff721dcdc7737c0e931c0473db3aadf4690f01dd5fc6da65188e21ecffd52ae
which is clearly completely different from the witness script initially. It is sha256 is 64b235d9fd37f2d68cb6edf19a25cc7765ef9c7299e3b448c86196cecd60feb0 which does not match the hash within the redeem script, so the script interpreter fails right here.
This script is decoded as
2 02f4e91f49be47c24571e100c501cc50e9c499e744a25e51e2153d26b856605952 02dbbedff721dcdc7737c0e931c0473db3aadf4690f01dd5fc6da65188e21ecffd 2 OP_CHECKMULTISIG
Taking a look at these two scripts, we will see the second has the keys flipped round. For some cause, the software program you used to finalize the PSBT modified the positioning of the keys within the script, which has resulted within the last transaction failing.
