Forum Discussion

Lewis_Beard's avatar
7 months ago
Solved

Anyone seen an Alerts page Header Graph error about java.lang.IllegalArgumentException?

I have some users with a role that, over the weekend, suddenly get an error on the header graph of their alerts page:

java.lang.IllegalArgumentException: Invalid operator

I suspect someone may have changed their role, but nothing shows in the audit logs for that role being changed, but I also know their dashboard has some broken items that exist in the correct place. And I’m suspecting the header graph has aggregated alerts in the database somewhere referring to things they cant see anymore and so is throwing the error. Because when I view the same thing for all alerts on the system (including theirs) I have no problems (my user can see everything).

I’m just wondering if anyone has ever encountered this sort of thing before. Maybe its a known product bug, throwing the error on the alerts page instead of just not showing what it cant see.

  • We’re hoping to have this resolved in v198.

    In the meantime as a workaround, you can add the “Resource Group (with subgroups)” filter to the page with a * glob expression as the value and the header graph should begin working again. 

5 Replies

  • Sarah_Luna's avatar
    Sarah_Luna
    Icon for Product Manager rankProduct Manager

    We’re hoping to have this resolved in v198.

    In the meantime as a workaround, you can add the “Resource Group (with subgroups)” filter to the page with a * glob expression as the value and the header graph should begin working again. 

  • Lim's avatar
    Lim
    Icon for LM Champion rankLM Champion

    Any progress on this? Everyone here is now getting this error on Alerts as well….

    Another update. This is resolved in platform release v198 which is planned to roll out starting next week in batches.

  • Any progress on this? Everyone here is now getting this error on Alerts as well….

  • Hi Lewis,

    Thank you for raising this in the community.

    I would like to know you that, we have not seen this error before and this has been raised to our Development team for further investigation.

  • Great information. 

    I had a recent engagement with a LM user experiencing this same issue just yesterday.