Inconsistent save interval
My server saves aren't working 100% of the time. The save interval is set to 900 seconds, yet every hour or so a save is skipped and happens 1800 seconds or 30 minutes apart, rather than 900 seconds or 15 minutes.
Sometimes it doesn't save for more than an hour.

I'm also having trouble manually saving.
Here's what shows up when I try server.save; "Invalidate Network Cache took 0.03 seconds"
I have looked around and seen that it's a normal message, so that probably isn't anything.

Anyone know what that means? Or how to fix this?
why did you change it to 15 minutes to begin with? when it does save what are your cache/write/disk times? server under a lot of load?

server is fine, even when no one is on it's still not saving. I changed it to 15 minutes just because I thought 5 minutes was too frequent, and each save caused a massive lag spike. I just woke up and my server hasn't saved once in more than 10 hours. I can't even save through Battlemetrics, I have to do it from in game on my server. Here's the latest save; "Saved 104,685 ents, cache(0.46), write(0.04), disk(0.01)."

Did you ever get this figured out?  I'm having a similiar issue as well.

The only reason I know of that a sever would suddenly stop saving is that a SavePause component is present somewhere. In vanilla Rust, these appear on cargo planes only, meaning that auto saves are paused while cargo planes are present on the map. Additionally, there have been past issues such as the following thread where a Cargo plane was present indefinitely but not visible and not technically even spawned.

https://umod.org/community/paratroopers/25074-plugin-causing-server-to-not-auto-save

If you don't see a Cargo plane anywhere, you probably have one that isn't fully spawned which was likely created by a bad plugin related to airdrops. In that case, you will need to use a specialized plugin to remove the unwanted cargo plane. Any experienced plugin developer could write such a plugin in 10 minutes. In absence of such a plugin, you will simply have to restart your server. You will also need to identify and remove the plugin that is causing the issue, or it will simply cause the problem again.