Timeouts in Pocketwatch – Resolved
06/01/2025 – 12:11 P.M. (AEST) We’re pleased to inform you that the issue causing timeouts on the Edit Shift pop-up has been successfully resolved. We sincerely apologize for any inconvenience
06/01/2025 – 12:11 P.M. (AEST) We’re pleased to inform you that the issue causing timeouts on the Edit Shift pop-up has been successfully resolved. We sincerely apologize for any inconvenience
26/08/2024 – 11:05 A.M. (AEST) We’re pleased to inform you that the recent technical issue related to Xero API request has been successfully resolved. We sincerely apologise for any inconvenience this
11/06/2024 – 04:00 P.M. (AEST) We’re pleased to inform you that the recent performance issue has been successfully resolved. System response times have returned to normal however we will continue
03/05/2024 – 01:10 P.M. (AEST) – We are pleased to inform you that the recent technical issue has been successfully resolved. Our Digital Signing provider experienced technical issues, leading to
01/05/2024 – 3:20 P.M. (AEST) We have identified the root cause of the performance issue affecting PocketWatch Reports and have taken steps to rectify the problem. System response times have returned
01/05/2024 – 9:16 A.M. (AEST) We have identified the root cause of the performance issue affecting Rosters in PocketWatch and have taken steps to rectify the problem. System response times
17/04/2024 – 6:00 P.M. (AEST) We’re pleased to inform you that the recent issue with PocketWatch allowance line Item not showing for non-roster managers has been successfully resolved. We sincerely
07/02/2024 – 12:25 PM (AEST):We’re pleased to inform you that the recent performance degradation of the system has been successfully resolved. We sincerely apologise for any inconvenience this may have caused
16/01/2024 – 11:58 AM (AEST): We’re pleased to inform you that the recent performance degradation of the system has been successfully resolved. We sincerely apologise for any inconvenience this may have
10/01/2024 – 10:01 AM (AEST): We’re pleased to inform you that the recent technical issue, which occurred between 7:38am and 7:46am (AEST), where users were not able to modify OR