Refresh
A module loads its lists when it is opened. Anything that happens afterwards — a colleague adding a record, or data arriving from a vessel — does not appear on your screen by itself. Refresh reads the data again and shows the current state.
It is available in every module, usually under More Actions.
Use it when you expect something to be there and it is not: after a colleague says they have entered something, after a data transfer has run, or when a list looks unchanged although work has been done on it.
What Refresh does not do
This is the distinction that matters most, because it is the most common misunderstanding:
Refresh does not fetch anything from a vessel. It re-reads the database your installation works with — nothing more. Data from a vessel reaches the office through the data transfer, which runs on its own schedule. If a vessel's entry has not arrived yet, no amount of refreshing will bring it in; the transfer has to run first.
When Refresh does not help
Some things are not held in the list but read once when the module starts — configuration settings and permissions among them. After a setting has been changed, or a right has been granted to you, close the module and open it again. Where even that does not help, the program has to be restarted.
If a record is still missing after all of this, and the data transfer has run, that is worth reporting to support — naming the record and the vessel it belongs to.