Handle a poor connection or a failed action

Previously loaded content may remain visible when a connection is weak. It can be older than what other collectors are seeing. Loading failures should not be read as proof that a store was removed or a product is sold out.

For a report, request, post, or setting change, wait for its success message. A preview or pending state is not the same as an accepted save. If a report’s delivery is not confirmed, retry inside the same flow; the acknowledgment may have been lost. A verification photo is different: after Send it keeps trying in the background for up to 15 minutes, so you don’t need to stay on the screen.

Restore your connection and use the offered Retry. Check the destination, history, or sent result before starting the same action again. If failures persist, note the screen, time, and exact message and send a bug report.

A working internet connection does not guarantee accurate indoor GPS. Conversely, a GPS fix does not guarantee that a report uploaded. Do not change the chosen store merely to work around a network problem.

A stock report appears in your report history and changes observations at an existing store. A Help location request appears in My locations and is checked before the directory changes. Check the matching history to confirm receipt instead of assuming one appears in the other.