I have…
- Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.
I’m submitting a…
- Regression (a behavior that stopped working in a new release)
- [ X ] Bug report
- Performance issue
- Documentation issue or request
Current behavior
E-Mail Rules sent 4 Times
Expected behavior
E-Mail Rule only sent 1 time
Environment
- [ X ] Self hosted with other version
Kubernetes Cluster where Squidex is running 1 time and a Worker Instance.
Version: 7.14.0
Somehow the worker sends the email twice and somehow the normal instance also is sending the email twice…
Do I have to configure something so that just the worker sends the emails?
Can you possibly give me a hint where to debug this?
No, there is nothing like that. Perhaps your worker config is just not correct or the server returns an error even though the email was sent.
Ah interessting, just had a look at the logs.
It seems that the worker also adds a rule job to the quenue
And whats also interesting, that there are 2 created events in the content type
and also the 2 jobs in the quenue
I am using the standard Helm Chart which you are providing.
Do you think it is a misconfiguration of the worker instance?
Looks like that. Perhaps you can verify the settings. Squidex logs them on start.
there i can only find this flag in both worker and normal instance
“clustering:worker”: “True”,
and there is a list of all services in the cluster with ip adress port and so on
So you have multiple workers running?
no there is just one worker
but there are other services in my kubernetes cluster, so all of my hosted websites etc…
I ma still confused. Have you checked the logs? There could be a bug in helm chart, I just want to be sure.
the logs look like this i removed the ip adresses 
Can you scroll to “worker”?
when i search in the log there is only “clustering:worker”
This is what I meant.
So this is true for both instances? Like the worker and the non-worker?
yes this is true for both, worker and non worker
Then it is a bug in helm, I will provide a fix asap.
1 Like
I have pushed a potential fix, but I could not test it yet.
wow great! will test it, tomorrow! 
1 Like
shouldn’t it be false?
just redeployed updated the helm repo and deployed the new version it is again true on both instances
