Sounds like this could be a potential defect. Which version and SU are you testing with? Are you saying it works if you don’t add a manual commitment?

In the scheduling information, in the SLA tab, what date are you seeing there?

Hi, 

I’m currently working with Application Service version 24.2.5

When I replicate the same scenario — using the same standard task, resource requirements, and location — but apply an SLA sourced from the Service Catalog, everything functions correctly and the task is scheduled as expected.

Here’s an example: 

When I add a Manual a commitment: 

• In PSO, the available time looks incorrect or inconsistent.
• In IFS Cloud, under Scheduling Information, there’s nothing showing — it’s as if the SLA is not recognised for scheduling purposes.

Hi, 

What values are displayed in the Scheduling SLA Types tab if all SLA Commitments are removed from the task? Is it empty in that case as well?

Hi, yes.

Here’s the situation:

In the Scheduling Dataset:

• Default Primary Scheduling SLA Type: empty
• Default Secondary Scheduling SLA Type: empty

In the Request Work Task:

• Activity Type: empty

As shown in the screenshot below, the Scheduling SLA Type appears empty because there’s nothing to populate if IFS doesn’t consider manual commitments.

Do you think is it a bug?

My expectation:
PSO should take into account the SLA that I manually added.

Do you think it's a bug?

Thanks 

Hi,

Got it. This is a defect and this is happening only for the SLA Commitments where the configuration is set to To Date. We already have a reported defect, and a fix will be available from 26R1 onwards. In the meantime, you can overcome this issue by using From Date or From Event as the configuration when creating SLA Commitments.