Bug: OOTB behaviour for Operational resource assignments in resource managmeent workspace

[Adrianadrian]

Hi all. We have encountered a strange and inconsistent problem which I would like to get some input one. We are implementering resource management workspace and have broad experience with RM, however we have been faced with a problem that is really bugging us. 

Other might have experienced this so please let me know if you have thoughts of the reason why the problem occur. 

Example:

I have two groups for resource management:

• Group A: 5 users
• Group B: 5 users

Goals:

1. Create an operational assignment for December 2025 for Group A. I want to create by selecting group (and not user)
2. Create an operational assignment for December 2025 for Group B. I want to create by selecting group (and not user)

Issue:

When I create an operational assignment for Group A, by creating on type group (and not specific resource) the system correctly creates one operational assignments per resource for December at 0.5 FTE each.

However, for Group B, the following occurs:

• When I create an operational resource assignment from December 1, 2025, to December 31, 2025 (one month), the system only creates one operational assignment for 1 out of 5 resources. This means 4 operational resource assignments are not created.
• When I create an operational resource assignment from November 1, 2025, to January 31, 2026, it correctly allocates 0.5 FTE per resource per month.
  
  This is very inconstent behavoir from the system

Summary:

Using the same procedure, I get different results for Group A and Group B. For some reason, the system is only creating one operational resource assignment for 1 out of 5 users in Group B, while it correctly creates one operational assignment per person for all 5 users in Group A.

Any one with a solution or reasoning here?

[jameswoodfo]

Hello,

If you are using Resource Assignments, they are highly dependent on the Employee Profile table. For the 4 users in group B, do they have the primary group as the group that you have created the operational resource plan for?

[Adrianadrian]

Hi @jameswoodfo . Thank you also for reaching out. This is also a post in:Re: bug/issue with operational resource assignment... - Page 3 - ServiceNow Community

Copying in the information on the latest relply. this will provide visualization of what is happening. All users have the same primary resource group, same schedules, and capacity is generated for all through UI action. The difference is that one resource have employement end date 30.11.2025 which creates the issue in where the system starts skipping records. See example B)

Hi @Josh Sutton . Really appreciate for reaching out. You too @abhinaykumar . Please look into this comment as I hope it will be clearer what the issue looks like. I have also updated the post with these screenshots.  I will describe the problem here more in depth and I will provide some screenshots below, Let me know what you think about this. Very curious on what why this is happening.
 Just fyi:
All users in the group below have same schedules, and capaciity is generated with UI action. All have same attributes, expect that one user, user #4 has employement end date 30.11.2025

Example A) - creating a group assignment with start date after employement start date, and end date after employement end date. This works as expected. See picture 🙂

Example B) Creating a group assignment with start date after employment end date for the user in the group.
This works not as expected/only partly.  Skips creating a record for the user who had an employment end date of 30.11.2025, which is correct.

 
However, it then skips creating records for other users in the group and only creates for user 2.

Our hypothesis is that when the system generates records and it comes to the next person with no capacity, it skips creating records for the next groups. 

[Adrianadrian]

@jameswoodfo . We have a support from ServiceNow on this now. The assumtion we have is the employment date. When creating a operational resource assignment on a group the system skips creating records when the start date has passed the employment end date. Problem is the once hit its the user it skips for other users in the group with no set employement end date

[Josh Sutton]

Cross posting my response from your other post regarding this question: https://www.servicenow.com/community/spm-forum/bug-issue-with-operational-resource-assignments-in-re...