IssueTracker

Component used: WorkManager
Version used: 2.7.1
Devices/Android versions reproduced on: Pixel 4 A/Adnroid 12

I have also a StackOverflow ticket raised for the same issue:
https://stackoverflow.com/questions/71130743/workmanager-loses-data-for-satisfied-content-trigger-on-cancelled-while-waiting  (only the package name is changed from com.acronis.abc.debug to com.myapp.test.debug)


I have a period of time where my Work is not executed. Also, I have not canceled it, rescheduled it, or done anything that can affect its behavior.  So I don't see a way for me to break the functionality of the JS.

But at the same time I see the following log:

-4s021ms   START: #u0a443/93  com.acronis.abc/androidx.work.impl.background.systemjob.SystemJobService
    -3s468ms  STOP-P: #u0a443/93  com.acronis.abc/androidx.work.impl.background.systemjob.SystemJobService cancelled while waiting for bind

And every time this happens I see that job with id 93 is rescheduled(same job id, but new enqueue time), but it starts with Unsatisfied CONTENT_TRIGGER.

I have checked the "Registered jobs", the "Recently completed jobs", and the "Job history". Please check the 2 files and you will confirm my conclusion. Check for: "com.acronis.abc.debug"

My expected result is if the job is canceled by the system and rescheduled - it should keep  CONTENT_TRIGGER as Satisfied.