I'm using WorkManager to schedule some periodic work, to synchronize a local DB with a remote one. Everything worked fine for months, until one day the DB stopped the synchronization. I found out through Stetho that all my Work instances had "schedule_requested_at" value equal to -1.
PeriodicWorkRequest refreshCpnWork = new PeriodicWorkRequest.Builder(MainWorker.class, Constants.WORKER_INTERVAL_MIN, TimeUnit.MINUTES)
.addTag("PeriodicWork")
.build();
WorkManager.getInstance().enqueue(refreshCpnWork);
This is the way I schedule my work, and as I said it worked fine for months. But from a certain moment it stopped scheduling my work, and in the picture instead of a correct timestamp there is -1.

I found out what is the meaning of -1 in schedule_requested_at.
From WorkSpec.java (work-runtime:1.0.0-alpha11):
If the value is -1 the work has been inserted into the table but it hasn't been scheduled yet.
In my case there were too many Work instance to schedule something new, following this query coming from WorkSpecDao.java: