Discussions

We are curious to find out why we have so many old shift records that are still in an "unpublished" state that get returned from the GET SHIFTS api endpoint. We understand that at first a shift may appear "unpublished" because it was recently generated and will soon move to the "published" state by way of its timestamp changing, but we are curious about some shifts (from years ago in our case) that are still in an "unpublished" state and how we can make sense of them.

Best,

Jack