Workload Migration

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Sun Apr 20 11:24:55 UTC 2025","trace":null}Information

• The following page contains information on the workload migration which is performed when updating to Release 41.5.

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Sun Apr 20 11:24:56 UTC 2025","trace":null}Background

• In earlier releases, recorded hours worked were mapped to the user via the e-mail address.

• Since this could cause problems when addresses changed, from Release 41.5 onwards the user ID is used to map the hours worked.

• During the update to Release 41.5 existing data is being migrated accordingly.

• In case the system already contains data which was not mapped correctly, it needs to be corrected manually.

Correction of Unassigned Records

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Sun Apr 20 11:24:55 UTC 2025","trace":null} Information

• If there is time recording data which can not be assigned to a user after updating to Release 41.5, the global admins are notified via an in-app notification.

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Sun Apr 20 11:24:55 UTC 2025","trace":null}Procedure

• Click Learn more & fix at the end of the notification.

• In a separate view, the e-mail addresses which could not be assigned to a user are displayed.

• Click the {"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Sun Apr 20 11:24:55 UTC 2025","trace":null} to assign the corresponding users to the addresses.

• When all addresses are mapped, click Re-Run Migration.

• If the migration is carried out successfully, a confirmation is displayed.