FileMaker 15 and 16 are wonderful at keeping record data in cache files even when you close the file and reconnect to the server.
I inherited a solution that when the data is stale it takes 2 minutes to start up again. Bad design.
So as not to mess anything up I moved an instance to a local Mac FMS16 server for debugging.
The first time I opened it I monitored Top Call Monitoring and saw the multiple millions of microseconds scroll by.
I want to see it again! But everything is now cached and it blipps open in less than two secs.
I tried going into each of the files and modified a record in a table manually... It did not force a "compare modification counts" Would I have to go to every table and modify each?
I looked for cache files to throw away on both client and server... No luck Restarted the server.... Nope Looked at the fmsadmin for flush cache.... Nope
Under load all the tables are being changed so everyone experiences the 2 min delay.
Is there an easy way to debug this?