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
Currently, there are two standalone operations in a sequence i.e. a backup with BACKUP_STARTED and BACKUP_FINISHED, right after the upload starts. There are pros and cons of this approach:
Pros:
Many backups can be done on the edge device in offline mode and when online they can be uploaded.
Clear visibility of the operations i.e. if there is a fail in the backup it's clear that this fail is in the backup preparation.
Cons:
BACKUP_FINISHED is reported but the backup is not uploaded on the backend.
The disadvantage seems serious and cover the typical/normal flow of the feature. That's why this ticket aims to revise and clear the issue.
The text was updated successfully, but these errors were encountered:
Currently, there are two standalone operations in a sequence i.e. a backup with BACKUP_STARTED and BACKUP_FINISHED, right after the upload starts. There are pros and cons of this approach:
The disadvantage seems serious and cover the typical/normal flow of the feature. That's why this ticket aims to revise and clear the issue.
The text was updated successfully, but these errors were encountered: