Thanks for the follow up. Yes indeed, the graph needs to be loaded again for it to serialize back into the correct type since it is not handled at deserialization time alone. I understand that this might not be as convenient as it could be. I will try find a better solution, possibly serialize back the graph automatically, or at least make the error able to point to the graph in question (which is something I am already planning to do anyway).