What version of Pulse are you using? This issue was fixed recently.
we use this version of pulse:
That issue was fixed in 5.7.3. We are finalising the testing of a new version at the moment so a new release will be out soon if you would prefer to wait.
perfect, thanks for your help.