Skip to content
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

Closed
2 tasks done
navins94 opened this issue Jan 16, 2024 · 0 comments · Fixed by #1016 or #1047
Closed
2 tasks done

Same data-point submitted 3 times when reopen the app #958

navins94 opened this issue Jan 16, 2024 · 0 comments · Fixed by #1016 or #1047
Assignees

Comments

@navins94
Copy link
Contributor

navins94 commented Jan 16, 2024

navins94 added a commit that referenced this issue Jan 16, 2024
dedenbangkit added a commit that referenced this issue Jan 17, 2024
ifirmawan added a commit that referenced this issue Jan 19, 2024
ifirmawan added a commit that referenced this issue Jan 19, 2024
@ifirmawan ifirmawan self-assigned this Jan 22, 2024
@ifirmawan ifirmawan linked a pull request Jan 22, 2024 that will close this issue
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 ifirmawan linked a pull request Jan 24, 2024 that will close this issue
5 tasks
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants