This does resemble a defect that was present in a not too distant version of SGPro. Please make sure that you are using the most recent version of SGPro 4.2 and, if the issue continues to occur, please send us logs showing the failed AF run. Guidance for sending logs is here: