Description
A regression has been introduced in Tokyo that impacts instances with gateway shard and if the instance has sys_audit in the sharded DB. The history set is not built correctly for the sc_task table, as a result, users are not able to see the recent activities on the Activity Formatter.
When an issue appears some of the symptoms users will see:
- Adding a comment or work note is not captured on the Activity Formatter
- Updating any field value is not reflected on the Activity Formatter but the field value is changed correctly.
- If history is already built, sometimes users can also notice it's showing a wrong history on the Activity Formatter.
Please Note, this issue doesn't cause any data loss. The field values are changed correctly and added to the sys_audit table. But the update is not captured in the sys_history_set table and hence is not reflected on Activity Formatter.
Steps to Reproduce
1. Login onto a Tokyo instance with a shard DB, where the sys_audit tables are part of the gateway table configuration
2. Open an existing sc_task record
3. Add a comment or work note, or update a field value
Note that the Activity Formatter does not contain the comment, work note, or update a field value, and it does not appear in record history as well.
Workaround
Unfortunately, we dont have any workaround to prevent or correct the issue.
We are actively working on the fix and will have the fixed version added under Fix Targets.
Related Problem: PRB1631253