A place to ask questions, connect with others, and stay in the know
Since you do not see the 'Load more history', then it suggests for that schedule and agent shift, that there is no published shift history (i.e., their shift hasn't changed since initial publish for this schedule period). If you can reproduce the issue after having modified the shift in a published schedule, then I would recommend opening a support ticket.The only other way I could duplicate similar is if I have a completely unchanged published shifts, make several edits that amount to ultimately no change (e.g., I moved a break out 15m and then back in). In that case I would see the two changes, but when I publish and then look at shift history it shows 'The selected shift has no history' because there was no delta with the changes cancelling out.
Not relevant to this, but wanted to comment further on the 'Load more history' button... It will be shown if there was a prior published schedule and an entirely new schedule was created and then was published - load more history would load the prior published (for the same time period) shift history when looking at the 'replacement' published schedule.
Every year, Genesys® orchestrates more than 70 billion remarkable customer experiences for organizations in more than 100 countries. Through the power of our cloud, digital and AI technologies, organizations can realize Experience as a Service℠, our vision for empathetic customer experiences at scale. With Genesys, organizations have the power to deliver proactive, predictive, and hyper personalized experiences to deepen their customer connection across every marketing, sales, and service moment on any channel, while also improving employee productivity and engagement. By transforming back-office technology to a modern revenue velocity engine Genesys enables true intimacy at scale to foster customer trust and loyalty.