Skip to main content

Why Unassigned Tasks on Team Management Dashboard sets to zero when the page refreshes?

When the user loads the dashboard, we initially limit the total amount of journeys pulled for performance (e.g., we only get the first 50) -- otherwise, we would potentially have a situation where the dashboard (which is often the primary landing page) takes several seconds to load which is a bad user experience.

So, when the user hits the dashboard, we do not pull in all the information, and we do not pull in those initial counts. When the user interacts with one of those two headers (Journeys or Unassigned Tasks), we pull back the counts as a second call.

Did this answer your question?