Error when creating a backup

I do know that in 2026 there are some changes (V4 api) and regression in the backup migration

I haven’t heard of anything in 2025 however.

Some troubleshooting

1. Check the flow notification > topics and search for the systemevent_error_log and confirm it is indeed missing. I’m not familar with this topic myself… was it a topic you had in a previous deployment?
2. Each backup job runs a task. Under System Config > System Events, you can search/fitler to find the “Error message logged” Once you find the task number, you can go to Resources → Logs → core
   1. the task number log file might shred more info

Best you reach out to Safe Support FME Support Center providing all the environment, namely listing out components of your fmeflow config file

Hi,

Thanks for your reply.  I did check the topics and there indeed is no such topic SYSTEMEVENT_ERROR_LOG. 

I did check the system even logs already and from there I could figure out where the error originated. It was an automation that was triggered by a “FME Flow system event (received)” and the selected event being “Error Messaged Logged”.

I was eventually able to get rid of the backup error. Here are the steps I took:

• When I changed the trigger to a different event, there was still an error when creating a backup, just reporting a different topic missing.
• When I changed the type of trigger to, for example, “Manual trigger” there were no errors during backup. Changing it back resulted in the error appearing again.
• Finally, when I duplicated the automation and deleted the original (or changed the trigger type in the original), the backup was also running fine! 

So that solved my problem. (Took me quite a lot of time though 😅). I still have no idea what caused this, but at least our system is backed up again

I stumbled upon this issue when someone has uploaded a Worksapace which had exacly the same name as already uploaded. Apparently there has not been an issue to upload Case insensitive workspace names, but it was for backup procedures. 😅 That resulted in SYSTEMEVENT_ERROR_LOG. 

Thankfully, there has been an article where I could trace back the issue and eventually found a workaround.