It could be a bug, see here. The solution in that case was to use the workflows device and put the filter there instead.
workflows