The Farmwalk iPhone app keeps captured photos, video and voice notes in a local upload queue until they can be sent. A saved capture is not the same as a successfully uploaded and linked evidence record.
Check upload status
Open your farm and go to the Capture tab.
Open Uploads to see waiting, active, completed and failed items.
Check any error or warning beneath an item. A photo can be uploaded while its evidence link or inspection observation still needs attention.
The queue can contain captures from more than one farm or project on this device. Check that you are working with the correct capture and farm before changing its links.
When signal returns
The app attempts queued uploads when a connection is available. Reopen the app and check progress; do not assume uploads finish while the app is closed. For failed items, use Retry, or Retry all to retry failed uploads together.
With farm accounts enabled, a farm capture refused because of access can remain parked for a fresh upload attempt after you sign in again, provided the new session also has that feature enabled. If its Uploads row offers Share, use it to export the local capture while you resolve access. Share is only offered for these parked captures while the feature is enabled and the file remains on the phone; it is not available for every failed upload. Export before manually using Retry or Retry all if you need a backup, since manual retry removes the parked Share action. Sharing does not upload or link the file in Farmwalk. If Share is absent, retain the queued capture and ask support rather than cancelling needed evidence.
If a farm is being updated or has moved
In app versions and services that support these responses, a farm being updated can temporarily hold an upload. Keep the capture in the queue and let its scheduled retry run; a hold is not proof the upload has completed. If the app asks you to update, use the App Store update action and check the queue afterwards. Do not uninstall the app or cancel a needed capture to clear the message.
If the error says the farm has moved to another FarmWalk service, keep the capture and ask the farm's owner or support how to reach it. The app does not automatically transfer your local capture to the other service. If retries continue to report an upload conflict, retain the item and contact support rather than cancelling it.
Correct evidence links
For an eligible farm capture that has not completed, use Link to choose an agreement action. This sheet does not offer a task or parcel picker. To carry a task into capture, start from that task's Capture action; check the recorded parcel separately. You can also tap Select, choose eligible waiting, failed or uploaded items, and use the bottom Link button to apply an agreement-action assignment to several captures. Select captures from the farm currently open: the queue shows other farms too, but the link choices belong to the current farm. For uploaded items, check the resulting evidence date and links on the web; bulk linking creates a new link and does not promise to remove an older one. Items currently uploading are not selectable for bulk linking. Inspection captures and the project Uploads screen do not use farm evidence linking.
Cancel and clear
Cancel removes that queue item and its local capture files. Only use it if you no longer need the capture. Clear completed uploads clears completed rows from the local upload history; it is not a vault deletion action.
Keep the app installed and retain needed captures until you have checked their upload and link status. If retries keep failing, keep the item in the queue and contact support with the displayed error, without sharing login codes.
The queue is not permanent original storage
Successful upload completion removes the local capture file. Completed history rows are normally pruned after 24 hours, except rows retained in an active batch. Preserve any separate original you need before completion; do not assume every capture has a Photos backup. Clearing history is not online evidence deletion.
If an agreement action is missing from Link, check it on the web. The native picker loads active agreements with limits and can omit items when a request fails; a missing choice does not prove that the action does not exist.
