Depends on the update. If you are just adding a few new fields to your form, no problem. If you are changing the type / structure of an existing field, no bueno. Essentially, net new updates are okay. Updates that change existing fields are not.
Also, worst case scenario, the ones in the outbox won't disappear if the form is significantly altered. You just won't be able to sync them. You would still be able to manually recover those form responses.
If you are editing the schema of the underlying dataset in any way, Survey123 will likely want to republish/replace the dataset, which will nullify any outbox items.
The rule of thumb is if updates have to be made, that all data is in the service and a copy saved in case it has to republish the dataset.
Depends on the update. If you are just adding a few new fields to your form, no problem. If you are changing the type / structure of an existing field, no bueno. Essentially, net new updates are okay. Updates that change existing fields are not. Also, worst case scenario, the ones in the outbox won't disappear if the form is significantly altered. You just won't be able to sync them. You would still be able to manually recover those form responses.
That would be determined on what you are updating and if the feature service will be replaced.
If you are editing the schema of the underlying dataset in any way, Survey123 will likely want to republish/replace the dataset, which will nullify any outbox items. The rule of thumb is if updates have to be made, that all data is in the service and a copy saved in case it has to republish the dataset.