There will be a breaking change in WorkQueueEntry entity behaviour.
The problem: Each work queue class has a data structure defined for work queue entries. This data structure lists all the data fields explicitly. The new functionality adds a new field that specifies number of retries to each work queue entry.
That means all existing work queue entry data structures have to be modified.
Solutions:
- We migrate so when upgrading model we add these fields for all the data structures used inside work queue classes
- We make the code backwards compatible – if the new field is not there we don’t complain unless retry functionality is turned on. Then we throw en error.