created and created_at for SHIFTS can have very different timestamps but seem to have the same meaning

We rely heavily on your SHIFTS GET endpoint to be the source for one of our ETL processes. We are having issues with the created_at property being much newer than the created property timestamp. The assumption is that these should be the same value no matter what, but as we go back historically (specifically starting on 2018-06-01) the created_at properties timestamp is always '2018-06-02 16:05:22.000' and the created properties timestamp can be as much as two years earlier.

We are curious to know if the date 2018-06-02 was a significant date for the SHIFTS GET endpoint and if that is the reason the created_at properties timestamp is seemingly stuck on the aforementioned date.

Best,

Jack