You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Collect should always send submissions in oldest to newest (in terms of finalization date). This will limit the number of out of order entity updates that servers will have to deal with.
Currently, submissions are either sent in display order (for manual sending) and database order (for auto send).
We should make sure we use oldest to newest order for these operations:
Auto sending forms
Bulk finalising drafts
Manually sending a selected set of forms
They don't all need to be fixed in one PR (or even released at the same time).
The text was updated successfully, but these errors were encountered:
seadowg
changed the title
Send submissions in oldest first order (to minimise out of order updates on server)
Send submissions in oldest first order
May 7, 2024
@lognaturel I've added bulk finalisation here as we could end up auto sending in the wrong order if we bulk finalize in the wrong order in cases where the sending happens very quickly (i.e. we get spin up multiple auto send tasks).
@grzesiek2010 I think you're going to take this one on, right? Would be good to prioritize it so we can test it along with some of the other interesting offline Entities cases. Thanks!
Collect should always send submissions in oldest to newest (in terms of finalization date). This will limit the number of out of order entity updates that servers will have to deal with.
Currently, submissions are either sent in display order (for manual sending) and database order (for auto send).
We should make sure we use oldest to newest order for these operations:
They don't all need to be fixed in one PR (or even released at the same time).
The text was updated successfully, but these errors were encountered: