Dashboard application filtering broken

Since the last update on the UI I can no longer filter applications.

Maybe this helps:

This also applies to filtering in the terminal. Same error.

This should have gone under balena cloud. Sorry.

This is the error message that seems to cause this:

vendor~scripts.a7db9d3f02196982a880.chunk.js:31 Unhandled rejection Error: Mixpanel error: NaN    at https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:130:395067    at r (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:130:442156)    at XMLHttpRequest.o.onreadystatechange (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:130:443107)From previous event:    at B.H [as _captureStackTrace] (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:31:36205)    at B._then (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:31:62656)    at B.then (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:31:61006)    at https://dashboard.balena-cloud.com/scripts.bcb086b5d1581686f349.js:1:287049    at Pa (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:77699)    at us (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:84828)    at cs (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:85008)    at ds (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:91146)    at $s (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:98488)    at Zs (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:97868)    at iu (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:99243)    at Ln (https://dashboard.balena-cloud.com/vendor~scripts.a7db9d3f02196982a880.chunk.js:89:30629)

Hello, thanks for reporting this. We are aware of the issue with the filters and are already working to have it fixed and deployed soon. We are tracking progress in this I have attached it to the ticket so as soon as the issue is closed you will get notified by as support agent.

This is now fixed.