[2023-03-01 12:52:49] open-ils.hold-targeter [INFO:2438457:HoldTargeter.pm:404:167769675124397182] targeter: [hold 1451044] exiting => Hold is not eligible for targeting
I'm not sure if just taking off the extra check for a frozen hold in "sub target {" in Utils/HoldTargeter.pm is the way. Or if there should be a separate mode just for handling frozen hold retargeting. I'm happy to test again in the future though.
I tried placing a new hold and using the suspend immediately option. I checked and there were no action. hold_copy_ map entries for the new hold.
I ran the hold targeter with the --retarget-frozen option and I can see that the hold targeter is trying to process the hold,
[2023-03-01 12:52:49] open-ils. hold-targeter [INFO:2438457: HoldTargeter. pm:404: 167769675124397 182] targeter: [hold 1451044] processing...
[2023-03-01 12:52:49] open-ils. hold-targeter [INFO:2438457: HoldTargeter. pm:404: 167769675124397 182] targeter: [hold 1451044] exiting => Hold is not eligible for targeting
I'm not sure if just taking off the extra check for a frozen hold in "sub target {" in Utils/HoldTarge ter.pm is the way. Or if there should be a separate mode just for handling frozen hold retargeting. I'm happy to test again in the future though.
Josh