--00000000000048675d05ff0717a9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable We are definitely not doing anything to create multiple shifts. If they shifts that don't belong in the schedule, they would delete those but not rapidly deleting and creating shifts. On Sun, Jun 25, 2023 at 10:39=E2=80=AFPM Angie Markwell wrote: > Can you all confirm we aren=E2=80=99t doing anything to cause this please= . > > Sent from Angie's iPhone > > Begin forwarded message: > > *From:* Mark Botticelli > *Date:* June 25, 2023 at 8:35:59 PM EDT > *To:* Melissa Reyes > *Cc:* Angie Markwell , Bjorn Cooley bcooley@thekey.com>, Chen Xie > *Subject:* *Re: Shift data in ClearCare* > > =EF=BB=BF > Thank you very much. > > On Sun, Jun 25, 2023 at 8:32 PM Melissa Reyes > wrote: > >> I have reached out to a few of my staffing leaders to inquire. Also >> checking in to see if the turning on of OT in CC URLs created this >> activity. >> >> Melissa Reyes >> >> ------------------------------ >> *From:* Mark Botticelli >> *Sent:* Sunday, June 25, 2023 3:51:49 PM >> *To:* Chen Xie >> *Cc:* Angie Markwell ; Bjorn Cooley > bcooley@thekey.com>; Melissa Reyes >> *Subject:* Re: Shift data in ClearCare >> >> Thanks, Chen. >> >> Melissa and Angie, looking forward to your inquiries. >> >> >> >> On Sun, Jun 25, 2023 at 6:47 PM Chen Xie wrote: >> >> Again, nothing here. Could this be from your new workday payroll export? >> >> On Sun, Jun 25, 2023 at 4:44=E2=80=AFPM Mark Botticelli > mark.botticelli@thekey.com> wrote: >> >> Can we inquire with the team as we need to make sure this isn=E2=80=99t = being >> triggered by us because clearcare was acting strangely. It will just >> eliminate a variable from the equation. Thanks so much. >> >> On Sun, Jun 25, 2023 at 4:40 PM Chen Xie wrote: >> >> Not that I can think of, Bjorn >> >> On Sun, Jun 25, 2023 at 4:15=E2=80=AFPM Bjorn Cooley wrote: >> >> Hi Angie/Chen/Melissa, >> >> We've been working to identify the root cause of the missed clock-ins an= d >> clock-outs this weekend. We've identified two issues, the first of which= is >> an API issue that ClearCare is working to resolve. >> >> The second issue is that some shifts are being created and deleted >> multiple times per day. Some are changing state every hour. This causes >> issues where a Caregiver loads a shift in their app, and then when they = try >> to clock-in later, that shift has been deleted. I expect this is an >> infrastructure issue on the ClearCare side, but wanted to confirm it's n= ot >> something the field is doing. >> >> Is there any reason the field offices would be rapidly creating, >> deleting, and recreating the same shift multiple times per day, starting >> last week? >> >> Thanks, >> Bjorn >> >> -- >> *Bjorn Cooley* >> Senior Director, IT >> bcooley@thekey.com >> [image: TheKey] >> >> >> >> -- >> >> >> *Chen Xie *CSO | >> *TheKey *650-208-2390 >> [image: TheKey] >> >> -- >> *Mark Botticelli* >> Chief Technology and Product Officer