Knowledge Base

FileMaker Pro requires an active network connection to communicate with a hosted solution. When your computer goes to sleep, that connection may be suspended long enough for FileMaker Server to end the session.

When a computer sleeps, it may shut down or suspend Wi-Fi, Ethernet, and VPN activity. FileMaker Server then sees the workstation as disconnected, even though FileMaker Pro may still appear open when the computer wakes. 

After waking, FileMaker Pro may reconnect automatically, display a communication error, or require you to reopen the hosted file. Uncommitted field changes can be lost if the connection ended before the record was saved.

If you need to remain connected during a long process, prevent the computer from sleeping until the process is complete. Do not disable security-related screen locking simply to keep FileMaker connected; screen locking and computer sleep can usually be configured separately. 

Before stepping away, finish data entry and click outside the current field so the record is committed. For long reports, imports, or scripts, confirm whether the process needs FileMaker Pro to remain awake or can be moved to a server-side schedule.

If FileMaker disconnects while the computer is actively in use, the cause may be Wi-Fi, VPN, internet, server, or network equipment rather than sleep. Send us the approximate time and error message so we can compare the incident with server logs and monitoring information.