The Refreshing Pilgrim
Reloadus hopefulus
Appearance
Easily mistaken for any other user, until the right foot begins its small devotional motion toward the F5 key. The eyes carry an expression somewhere between patience and betrayal.
Habitat
Slow-loading dashboards, third-party widgets, anything behind a status page that has not yet updated.
Field notes
The Refreshing Pilgrim does not believe the page is broken. It believes the page is merely tired, and that another reload will rouse it. One Pilgrim hit reload 14 times on a single 504 in under a minute. Faith, it would seem, is a renewable resource.
Resolution
Either the page eventually loads, validating the Pilgrim's worldview, or it does not, at which point the Pilgrim abandons silently and without complaint. Rarely files a support ticket. Believes it must have been their internet, which puts the internet provider in a worse position than yourself.
Hazards observed
A backend timeout your team has stopped noticing. An over-eager loading spinner that resolves visually before the data arrives.
If you spot one
A user who reloads the same page four times thinks it is stuck rather than broken, and they are usually right. Behind it sits a slow endpoint, or a spinner that finishes before the data lands. They will not file a ticket, so nobody on your team hears about it. A Monitor scanner flags any session that reloaded one URL three or more times, and the reload timestamp points straight at the endpoint.