The *arrs unfortunately don't really work that well with oneclick hosters. I had a setup of jdownloader combined with filebot and a sharehoster premium account once in a while, and then using Plex to access the media.
Since then I switched to *arrs in combination with Usenet and am glad I could leave the oneclick hosters behind. Especially when you are frequently paying for them, it's absolutely worth the money (Usenet providers and indexers are mostly paid and I would recommend against free ones).
If you are interested, this guide is an excellent entrypoint.
There should be entries in the history/logbook for the automation entity itself (automation.whatever). From there you should at least be able to determine, what changed the enabled state of your automation(s). If it is a service, you might have to search for specific calls of this service (e.g. in your other automations). It might also be an option to do a global text search for the entity IDs of your automations and/or any automation services. You could do this via the vscode addon if it is installed.
I myself have never encountered this error and got a few disabled automations, which haven't changed their state over months and multiple updates/restarts.
The *arrs unfortunately don't really work that well with oneclick hosters. I had a setup of jdownloader combined with filebot and a sharehoster premium account once in a while, and then using Plex to access the media. Since then I switched to *arrs in combination with Usenet and am glad I could leave the oneclick hosters behind. Especially when you are frequently paying for them, it's absolutely worth the money (Usenet providers and indexers are mostly paid and I would recommend against free ones). If you are interested, this guide is an excellent entrypoint.