We are aware of this issue but didn’t find the culprit yet. A systemctl stop zammad && systemctl start zammad should be more than enough.
systemctl stop zammad && systemctl start zammad
See: