This is an issue we had some time ago, and I wonder if anybody else ever had a good solution for this:
There was a process instance defined which should be started every night at 4am in the Europe/Berlin timezone. The server was running with UTC as the system default.
When entering or leaving daylight saving time, the job execution start “moved” for an hour every time, confusing people. Providing a timezone with a timer start event or cron job was not possible.
We ended up scheduling jobs with a Java based scheduler and started the process via the Java API, but I was wondering if there was a cleaner solution that we missed?