Skip to main content
Question

PSO version 6.16.0.46 Unable to rebook an existing activity

  • January 14, 2026
  • 2 replies
  • 17 views
D
Do Gooder (Customer)
Forum|alt.badge.img+7

It seems to me that this version of PSO (6.16.0.46) has serious issue when attempting to rebook an activity. Here is the description of the behaviour:

  • When sending for the first time the request for an appointment for an particular activity, PSO is always responding correctly with the available slots. 
  • If you save a specific slot, the activity is correctly showing on the Gantt chart. 
  • If you try to rebook that activity (customer calls back to change the date of his/hers appointment) on the same day - the sytem always send back Error 500 - An internal error ocours.
  • If you try to rebook the same activity the next day (of after you force the FSM-PSO initialization) you will have no problem to rebook that activity. 

I am able to demo this using Postman pointing to PSO 6.16.0.46 - IFSScheudlingRESTFull Gateway

Same payload work perfectly on 6.5.0.29 (and you can rebook the same activity as many time as you want) - so the issue is not with the payload. 

 

I will go ahead an open a Case, but I just wanted to see if anyone is experiencing similar issues with this version. 

2 replies

Sachitra_W
Do Gooder (Employee)
Forum|alt.badge.img+5
  • Sachitra_W
  • Do Gooder (Employee)
  • January 15, 2026

Hi ​@dsuciu

This is an assumption, as the two payloads—the original request and the rebooking request—have not been attached here. Based on your comment that you are testing with the same payload via Postman, I am assuming that the same appointment request ID is being used for the rebooking.

If that is the case, the appointment request ID should be changed to a new, unique value when rebooking. This requirement is also mentioned in the documentation.

 

 

D
Do Gooder (Customer)
Forum|alt.badge.img+7
  • dsuciu
  • Author
  • Do Gooder (Customer)
  • January 20, 2026

Hi Sachitra, 

I’ve attached the AppointmetRequest payload and the response. 

When we sent this to PSO 6.5.0.29, eveything works fine. We can book, rebook, move the schedule to another week and so on so for. When sending the same payload to PSO 6.16.0.46, at first we are able to get the correct available slots, but after we select the slot, we cannor rebook the activity as the system is returning :

INFO        2026-01-20 00:20:19,230 - 23 request sent successfully - {log4net:HostName=SS01IIS-20001} 
ERROR       2026-01-20 00:21:19,336 - 23 Error GetTimeSlots(): - {log4net:HostName=SS01IIS-20001} 
System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
   at System.Net.HttpWebRequest.GetResponse()
   at IFS360Service.ServiceClient.GetTimeSlots(ServiceRequest request)

I’ve attached all payloads we sent to PSO so you can review it. Again same payload works perfectly on 6.5.0.29 but fails every time when trying to rebook the same activity in PSO 6.16.0.46

Terms & ConditionsCookie settingsAccessibility statement