Hi,
I found a release note that may be related to what you're seeing:
https://help.genesys.cloud/release-notes/genesys-cloud/october-20-2025/
The October 20, 2025 release introduced enhancements to activity code mapping and adherence settings, including support for Primary Status and Secondary Status mappings for activity codes.
Since you mentioned that this is impacting your adherence calculations and scheduled activity codes, I'd recommend reviewing a few things:
Compare your current Activity Code mappings with what was configured before the update.
Verify whether any default activity codes now have a Secondary Status assigned and whether those mappings align with your operational requirements.
Review the Ignore for Adherence setting for the affected activity codes, as this can now be configured at the individual activity code level.
If possible, create or use a test activity code and validate how different Primary and Secondary Status combinations are reflected in Real-Time Adherence and the Schedule Editor before making changes in production.
Based on your description, this release may explain why you're now seeing secondary statuses on the default activity codes. However, if the behavior you're experiencing doesn't align with the documented enhancement or is producing unexpected adherence results, it may be worth opening a Customer Care case for further investigation.
I'd also be interested to know:
Which default activity codes were affected?
Is the impact only that secondary statuses are now displayed, or have the adherence calculations themselves changed?
That additional information could help determine whether this is simply the expected behavior after the enhancement or something else.
------------------------------
Raphael Poliesi
------------------------------