​@Augustin Hmmm. I was able to filter by my device name and not see that issue.

I might recommend contacting support@automationanywhere.com for further assistance.

Hi ​@Augustin,

You may try the following and see if it helps or not.

1. Go to the user profile in the Control Room.
2. Remove the Bot Insight license and save this change.  (This is if you have the Bot Insight license)
3. Reload the Dashboard.
4. Go to the user profile in the Control Room again.
5. Assign the Bot Insight license again and save this change.
6. Reload the Dashboard.

Note: For scenarios where the Business Dashboard is created in the DEV environment and bot runners are on PROD or UAT, the Dashboards need to be ​​migrated by exporting the bot from the DEV Public repository (Checked-In) and importing it to PROD or UAT. After that, the bot must be executed once using a bot runner account. Finally, you will be able to see the migrated Dashboard.

Hi Pasmakumar,

Thanks for your answer.

I have tried to remove and re-assign the Bot Insight license twice but it did not solve my problem.

Regards,

Could you please clear the global cache in automation any =where folder which is present in program data 

Ok. You may try the following as additional breakfixing steps.

1. Try saving the dashboard without the Device Name filter, then reopen and add the filter, or publish from a different browser/session. 

2. Ensure your user has AAE_Bot Insight Admin and that the dashboard name has no angle brackets or disallowed chars when using Save As. 

3. Device names can include characters that break validation. Test by:

• Filtering to one runner with a simple alphanumeric device name.
• Avoiding long Selected lists (start with a few items).
• Using Include (not Exclude) first.
• The Attributes filter supports Device Name, but certain values can cause errors. 

4. If some selected devices were renamed, deleted, or show picked at runtime, the filter can fail. Remove those entries or refresh device metadata (Control Room → Devices). 

5. Clear the cache, try Incognito or another browser, then reapply the filter and Save As.

If none of the above worked, then I would also recommend raising a support ticket for this.