Thanks for reporting this issue, @Julien_RENAUD! Our product team identified this error and it seems this happen when you have at least two custom field filters in a chart. We have deployed a fix and this issue should be solved soon. I’ll keep you posted!