Performance Degradation – Resolved
15/01/2024 – 11:36 AM (AEST): We’re pleased to inform you that the recent performance degradation in Pocketwatch where some pages were timing out has been successfully resolved. We sincerely apologise
15/01/2024 – 11:36 AM (AEST): We’re pleased to inform you that the recent performance degradation in Pocketwatch where some pages were timing out has been successfully resolved. We sincerely apologise
Between 7:30 PM and 7:56 PM (AEST), we encountered a temporary slowdown in response times on our platform. Our monitoring team promptly identified and resolved the issue to restore optimal
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
22/11/2023 – 11:45 AM (AEST): We’re pleased to inform you that HICAP have successfully resolved their issue. All invoices can now be successfully claimed. We sincerely apologise for any inconvenience this
15/11/2023 – 3:01 PM (AEST): We’re pleased to inform you that the recent technical issue with bulk uploads from GENIUS not generating has been successfully resolved. We sincerely apologise for
15/11/2023 – 5:00 PM (AEST): We’re pleased to inform you that the recent issue with system unable to save and approve invoices after OCR scan has been successfully resolved. We
20/10/2023 09:47 AM (AEST) We’re pleased to inform you that the recent technical issue has been successfully resolved. The filters in the timesheets and reports are now fixed. 20/10/2023 08:42 AM (AEST)
18/10/2023 – 6:15 PM (AEST): We are pleased to announce that all requests have been processed and this issue is fully resolved. We sincerely apologise for any inconvenience this may
18/10/2023 12:07 PM (AEST): We’re pleased to inform you that the recent technical issue has been successfully resolved. All the checkouts have been processed and the timesheets are now up
08:47 AM (AEST) – 17/10/2023: We are pleased to inform you that we have restored regular service and consider this incident resolved. However, the database team will continue to monitor