Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
User Problem
Currently, in response to the payload sent by the schedule timeline API endpoint, We send two objects, historical and default when the rotation starts and ends between two different dates. The end time in historical has the today's date and the end time in default has the actual date.
Suggested Solutions
Give a unique ID for the same rotation that starts and ends between two dates or give them as one entry in the response payload.
Current Workarounds
Currently, you need to match the user ID and type to find the start and end date.