Troubleshooting the Gamification app
The logic: This is usually caused by a "zombie" connection where the UI calls an Action Flow ID that no longer exists. Since the app can't "find" the flow, the UI components stay in a loading loop.
The fix: Re-establish the bridge between the UI and the automation engine:
Request the official Action Flow Blueprint from Celonis Support.
Delete non-functional flows and import the new blueprint.
Update the links in the "Add new Assignment" and "Admin View" to point to the new IDs.
The logic: Augmented attributes are custom metadata layers. When you duplicate a Data Model, these layers often don't copy over, leaving the app looking for "ghost" columns.
The fix: Re-create the Gamification data model from scratch rather than copying an old one. Connect this new model directly to the app to ensure attribute definitions generate correctly.
The logic: This involves a "snapshot and clear" strategy—ignoring old data via a date filter and providing fresh table containers for new scores.
The fix:
Update the
GamificationStartDateparameter in the Data Pool.Archive old data using the following SQL:
ALTER TABLE "Assignments" RENAME TO "Assignments_Backup_2024_Q1"; ALTER TABLE "Points_Allocation" RENAME TO "Points_Allocation_Backup_2024_Q1";
Run the transformation "Create Tables: Points Allocation & Assignments" followed by your data job.
The logic: The app UI protects data integrity by omitting a delete button. You must either purge the record via SQL or filter it out of the UI view.
Option A: Permanent delete (SQL)
DELETE FROM "Assignments" WHERE "id" = 'CHALLENGE_ID_HERE';
Option B: Soft delete (UI filter)
To hide challenges without losing data, update the status to "Hidden" and apply this PQL filter to your components:
FILTER "Assignments"."Status" != 'Hidden';
The logic: Points are calculated by a data job scanning for "Completed" statuses. If points don't appear, the data pipeline is likely failing to bridge the activity from the source system to the Gamification tables.
The fix:
Ensure the Gamification data job ran after the activity occurred.
Verify the
UserIDin the activity table matches theUserIDin the Participants table (this is case-sensitive).Use the Manual Point Allocation action flow for specific edge cases.
The logic: Participants are pulled from a member details table. Restricted app-key permissions often prevent the app from "seeing" new users.
The fix: Ensure the Application Key has "View All Users" permissions and manually trigger the "Member Details" data job to sync the Celonis user list.
The logic: This is typically a filtering issue where team names in the data do not match the mapping in the Knowledge Model variables.
The fix: Verify the Team_Mapping variable in the Knowledge Model and check that the user viewing the component has the necessary data permissions for those specific users.
The logic: Action flows deactivate after consecutive failures, often due to expired tokens or null values being passed to mandatory fields.
The fix: Re-authenticate the connection in the first module and enable "Incomplete Executions" in the flow settings to allow for troubleshooting without deactivation.