Class UUID doesnt match - Handling app updates

Just trying to wrap my head around the following scenario:

User uses my app while offline, creates different system entities which in turn create jobs which require network and are therefore persisted to storage to wait until we get network access.

User turns off app.

User enables network, receives an app update. Update includes changed class files. User opens app, now triggering the jobs to run but now fail due to the Class UUID no longer matching to what was initially there when it was persisted.

What is the correct way to handle a situation like that?