
AgDiary
Management app for stations
About
What's New in AgDiary
4
November 13, 2026
This one is mostly things that were quietly not working. If you keep safety records on the phone, start with the first bit. SAFETY RECORDS THAT WERE NOT GETTING THROUGH Incidents have never synced, at all. Any incident filed on a phone is still on that phone, and it goes up on the first sync after you install this. Every incident was recorded as "not notifiable", including the ones where the box was ticked. Worth a look at your register once they land. Visitor sign-ins have been refused since 16 August, with nothing on screen to say so. The ones still sitting on a phone will go up now. Hazards with a typed status were refused as well, and the form's own placeholder suggested a word the server rejects. Status and category are pickers now, filled from the list the server publishes. The incident form also matches the register: the five injury questions the web form has always asked are in, and four boxes with nowhere to go are out. RECORDS THAT SAVED AND NEVER ARRIVED The same fault in five more places. Chemical unit and use type, fertiliser unit, fodder unit and fodder status were all typed in free hand, and anything off the server's list came back refused. "Litres", "Kg" and "tonnes" were all turned away. The fodder status box suggested wording the server does not accept, so the hint itself produced records that never left the phone. All five are pickers now. Fertiliser type is too, so one fertiliser stops showing on the register three times under three spellings. Toolbox talk topics and their talking points, fire danger ratings, horse sexes and rider levels, and competency assessment methods and outcomes were not loading at all. Those forms fell back to free text and the lists simply looked empty. They read the published lists now. A MOB OF ONE ACTUALLY MOVES Tick one mob out of a paddock holding more than one, choose where it is going and save: the entry went into the diary and the stock stayed where it was. Fixed here and on the server. IT STOPS GETTING STUCK Switch enterprise, or use Logout and wipe, then close the app and open it again, and it sat on the opened book and stayed there. Force-quitting made no difference. The wipe was throwing away the key to the app's own database. It starts clean now, and the silent sign-out that came with it is gone too. The overnight crash is fixed as well. That one was a fault in the toolkit the app is built on, and we now compile around it. If anything feels slower than it used to, say so, because that is the first place to look. PHOTOS A photo the server will not take now says so, under the button you tapped, instead of sitting in the queue retrying forever. Big iPhone photos are resized to fit, full resolution first, so a photographed serial plate is still readable. FLOOD CAMERAS Council road and creek cameras for your shires, with a slider back through the recent frames, stars for the ones you watch and a card on the home screen. Every picture carries the time it was taken. Over six hours old is amber, over a day is red and says STALE, because a clear crossing this morning is not news tonight. PADDOCKS AND FEED A feed estimate over 90 days old no longer shows figures nobody should be judging by. The paddock says "re-assess" in blue, on the map and in the feed list, and the home screen says how many need doing. Where the gates are open between paddocks, open one and scroll to RUN TOGETHER to have the group judged as a single grazing unit. "Shut the gates" splits them again. Before this, a paddock the stock had not been counted in could paint red beside its neighbour's green inside the one open-gated unit. Yards: drop a pin where they are and the app draws a 50 metre square, then drag the corners onto the real fence. The paddock screen also says how that paddock is going against its own record, instead of showing a number with no scale. REPORTS The LPA audit pack goes complete from a phone, and says how big it is first. On mobile data it asks before spending it.
More




