Transaction History Limited to the 50 Most Recent Records
The Transactions page requested its history without a record limit, so the API's default of 50 applied and older records could not be reached. The page now loads the full history and offers a date range filter.
22:46 GMT
Fix deployed to production.
22:10 GMT
Cause identified: the page requested its history without a record limit, so the API's default of 50 applied. Preparing fix.
21:30 GMT
Investigating reports of older transactions missing from the Transactions page.
"Scheduled Only" Toggle Cleared Entered Readings on Mobile
On the mobile entry pages, switching the "Scheduled only" filter rebuilt the form and cleared every value already typed. Entered values now survive the toggle.
22:36 GMT
Fix deployed to production.
21:50 GMT
Cause identified: switching the filter rebuilt the form and cleared every value already typed. Preparing fix.
21:15 GMT
Investigating reports of entered readings disappearing when the "Scheduled only" filter is switched on mobile.
Critical Thresholds Populated With Estimated Values
One of the routes for adding a water quality parameter to an exhibit wrote a starting critical range derived from the target range, rather than leaving it for the user to set. As a result some parameters carried critical thresholds that nobody had chosen, and alerts raised against them displayed those values. Affected configurations have been reviewed and a fix has been applied.
15 Aug, 10:17 GMT
Issue resolved. Affected configurations reviewed and corrected.
15 Aug, 02:11 GMT
Fix deployed to production.
14 Aug, 23:59 GMT
Cause identified: one route for adding a parameter derived the critical range from the target range instead of leaving it for the user to set. Preparing fix.
14 Aug, 22:30 GMT
Investigating an alert displaying a critical threshold that had not been configured.
Incorrect "Partial Success" Warnings on Mobile By System Entry
Recording readings across a water system on the mobile app sent each parameter to every exhibit in the zone, including exhibits where that parameter is not configured. Those readings were correctly rejected, so a normal submission still reported a list of failures. Submissions now go only to the exhibits configured for each parameter, on both the live and offline paths.
23:18 GMT
Fix deployed to production.
23:00 GMT
Cause identified: By System entry submitted each parameter to every exhibit in the zone, including exhibits where it is not configured. Preparing fix.
22:30 GMT
Investigating reports of "Partial success" warnings after By System submissions on the mobile app.
Unsaved Changes Prompt Required Two Presses on Mobile
Choosing "Leave anyway" on the mobile unsaved-changes prompt returned to the same page, so leaving a form took two presses. Navigation now leaves on the first press.
23:10 GMT
Fix deployed to production.
22:50 GMT
Cause identified: the prompt's "Leave anyway" action returned to the same page rather than leaving it. Preparing fix.
22:20 GMT
Investigating reports of the unsaved-changes prompt on mobile requiring two presses to leave a form.
Species Missing From Transaction and Inventory Dropdowns
Users were unable to find some species when recording a birth, mortality, transfer or departure. The species catalogue picker loaded only the first 200 species in the list. All species and animal pickers now load complete lists on desktop and mobile without truncating.
22:55 GMT
Fix deployed to production.
22:25 GMT
Cause identified: the species catalogue picker loaded only the first 200 species in the list. Preparing fix.
21:40 GMT
Investigating reports of species missing from transaction dropdowns on desktop and mobile.
Parameter Configurations Reported as Saved Without Being Stored
Adding a water quality parameter to an exhibit could report success while storing nothing when that parameter had previously been deactivated for a given exhibit. Removed or deactivated parameters are now restored with the new values when re-added, and a save only reports success when every write succeeded.
26 Jul, 16:52 GMT
Fix deployed to production.
25 Jul, 16:01 GMT
Cause identified: previously deactivated configurations were treated as already existing and skipped, and the bulk save reported success regardless of individual failures. Preparing fix.
25 Jul, 15:05 GMT
Investigating reports of parameter configurations confirming successfully but not appearing on the exhibit.
Backdated Fridge, Freezer and Weight Records Saved Under the Entry Date
Fridge and freezer temperatures and animal weights were stored with the time they were entered rather than the date selected on the form. Both record types now accept the selected date on desktop and mobile, and the date picker no longer allows a future date.
3 Jul, 16:52 GMT
Fix deployed to production.
2 Jul, 15:48 GMT
Cause identified: the temperature and weight endpoints ignored the supplied date and stamped records with the current time. Preparing fix.
2 Jul, 14:45 GMT
Investigating reports of backdated fridge, freezer and weight records appearing under the date they were entered.
Comments Unable to Be Added on Desktop
Users on the desktop platform were unable to add comments to out of range environmental readings. The issue was traced to a validation error in the comment submission handler. A fix has been deployed and comment functionality is fully restored.
16:27 GMT
Issue resolved. Comments are now being saved successfully across all desktop browsers. No data loss occurred during the outage.
16:15 GMT
Fix deployed to production. Testing comment submission across different modules.
15:52 GMT
Cause identified: validation logic incorrectly rejecting valid comment text. Preparing fix.
15:33 GMT
Investigating reports of users unable to add comments on the desktop platform.
Mobile App Crashes on Load
The latest mobile app version (v5.1) contained a service worker cache configuration error causing the app to crash immediately after launch. A hotfix version was deployed and users were advised to refresh their cache.
09:12 GMT
Mobile app v5.1.1 is now available and functioning normally. Users experiencing issues should clear their browser cache.
08:37 GMT
Cause identified: incorrect cache manifest path in service worker. Preparing fix.
08:15 GMT
Investigating reports of mobile app crashes on launch affecting v5.1 users.
Email Notification Delays
Alert and notification emails experienced delays of up to 15 minutes due to rate limiting from our email service provider during peak hours. Additional sending capacity has been provisioned.
17:27 GMT
Email delivery fully restored. All queued notifications have been sent and normal delivery times resumed.
16:53 GMT
Upgraded email service plan to increase sending limits. Queue is clearing.
16:22 GMT
Investigating delayed email notifications. Provider rate limits reached.
Database Query Performance Degradation
Users experienced slower dashboard load times and data retrieval delays due to missing database indexes on water quality readings table. Indexes have been added and query performance restored.
12:19 GMT
Performance restored. (<50ms).
11:35 GMT
Cause identified: missing indexes on site_id and recorded_at columns. Applying indexes now.
11:04 GMT
Investigating reports of slow dashboard performance and increased query response times.
Intermittent Mobile App Connectivity
Some users experienced temporary connectivity issues with the mobile app. The issue was resolved by restarting the mobile API gateway.
14:45 GMT
Issue resolved. All mobile services are operating normally.
14:30 GMT
Investigating connectivity issues with mobile applications.
Scheduled Maintenance - Data Collection API
Routine maintenance was performed on the data collection infrastructure to improve performance and reliability.
11:30 GMT
Maintenance completed successfully. All services are operational.
09:15 GMT
Beginning scheduled maintenance on data collection services.
Email Notification Delays
Alert emails were experiencing delays of up to 10 minutes due to increased email volume. Additional capacity has been provisioned.
17:20 GMT
Email delivery delays resolved. Alert notifications are being sent normally.
16:42 GMT
Investigating reports of delayed email notifications.