Galaxy Flex 3-20 stuck in bootloop?

My Flex 3-20 panel had been running fine for the last couple of months, until we had a power outage a few days ago.
The panel has a battery so it wasn't affected directly, but the power loss caused a com failed error, which requires a reset.
When I wanted to reset the panel, I shut it down via the menu, but it got stuck on 'saving configuration' for over 10 minutes, at which point I decided there was no other option than to pull the power...

It booted up OK after that, and ran for about 2 hours, until I got a com failed, memory ok, and boot up notification, after that it just keeps going through this cycle every 10 minutes. It does boot, I can also connect to it using the app, the keypad functions, but the main panel itself seems to shut down and start up again. The RF portal en IP module LEDs keep flashing, but the LED on the panel itself goes off.
Anyone familiar with this and has any idea what's going on? How do I diagnose (and fix) what's wrong here?

The only thing to try is storing the config with RSS (for restore), then flash upgrade the panel with the same or newer firmware in the event that the current one has become corrupted. The panel uses a journaling flash filesystem, so the newly uploaded program will be located in a new area of the flash chip. If it fails after that, then the PCB needs replaced.

Thanks for the reply!

After trying to eliminate possible causes I removed the modules and performed a cold start with just the panel and got called away for something, and to my amazement the panel just stayed on for 45 minutes straight or so.
I then re-added the modules, stayed on again for an hour...

I do wish I read your reply about the RSS config prior, I thought I made a backup last time, but I didn't...
Anyway, it's a small system without many complications, so fairly easy to reprogram, the only thing is it now has to relearn all the tags and RF serials, kind of annoying having to pry open all sensors again...

I intend to see if it's stable now for a week, if no reboots it's probably OK. I was already thinking about reflashing the firmware as a last step and will do that if it reboots again.
About the flash memory; do you mean that it allows only X writes and then it's done for? Or do you mean that if it writes to another part and is still corrupted, somethings else is fundamentally wrong?

The cold start doesn't renew the executable file, but it does renew the complete config tree. If the corruption was in the config tree, the cold start should resolve that.

Wanted to provide an update from my side:

Most likely it was indeed just the config tree, have reprogrammed everything and has been running for almost 3 weeks without issues now. So all is well after all.

Exports of config have been made and stored in 2 places after programming this time...

Thanks again GalaxyGuy!

Okay, hopefully it will remain without issue.