-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same data-point submitted 3 times when reopen the app #958
Comments
navins94
added a commit
that referenced
this issue
Jan 16, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 19, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
Each sync process will be managed based on the status of the job that has been created. If the active job is still incomplete and a new interval is initiated, the sync process will not run again in Foreground service.
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
Each sync process will be managed based on the status of the job that has been created. If the active job is still incomplete and a new interval is initiated, the sync process will not run again in background task.
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 22, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 23, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 23, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 23, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 23, 2024
5 tasks
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
…d attempt When the job has exceeded the number of attempts, the status is set to on progress to be handled in the next process to check the number of pending items. If the job status === ON_PROGRESS && pendingItems.length > 0 then Re-sync and reset attempt to 0 if the job status === ON_PROGRESS && pendingItems.length === 0 then delete the job
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
ifirmawan
added a commit
that referenced
this issue
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bugs
The text was updated successfully, but these errors were encountered: