Workload Balancer Showing Zero Hours | Community
Skip to main content
New Member
November 2, 2025
Solved

Workload Balancer Showing Zero Hours

  • November 2, 2025
  • 3 replies
  • 213 views

I am having an issue where I have users assigned to tasks however their hours are showing zero. This changed when I updated the task assignments to be their job role names instead of their actual user name because I am working with 300+ projects and want to resource level. Any insight into why their hours might be showing zero if they're assigned to a task with hours? Also note that each of the project tasks are set to start and end during work hours. 

Best answer by Lyndsy-Denk

It sounds like you might be looking at the top section of Workfront Balancer, which is dedicated to Unassigned Work (that is, tasks not yet assigned to a specific user). Once a task has a specific user assigned, it will drop to the Assigned Work section below.

3 replies

Lyndsy-Denk
Community Advisor
Lyndsy-DenkCommunity AdvisorAccepted solution
Community Advisor
November 3, 2025

It sounds like you might be looking at the top section of Workfront Balancer, which is dedicated to Unassigned Work (that is, tasks not yet assigned to a specific user). Once a task has a specific user assigned, it will drop to the Assigned Work section below.

Kurt_Jones
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 3, 2025

Sean,

This is a good resource link to bookmark, https://experienceleague.adobe.com/en/docs/workfront-learn/tutorials-workfront/manage-resources/resource-management/settings-for-users, as its connected to a series of content Adobe created to help with the understanding, configuration, and set up of resource management.  It might offer some additional insights.

If my response answered your question, please mark it answered, so others can find the answer
Level 2
January 29, 2026

I started having this same issue out of nowhere and I can’t figure out why. I’m going to submit a ticket to Adobe to help

Level 2
February 23, 2026

My issue was an actual bug acknowledged and fixed by Adobe. Resolved