Troubleshooting

Check these in order:

1. Challenge status: Rules only fire when they are part of an Active challenge. Verify the challenge is not in Draft, Paused, or Ended status.
2. Rule status: The rule itself must be set to Active. Deactivated rules are ignored by the engine.
3. Trigger type: If the rule uses Create, it only fires on new records. If it uses Update, it only fires on edits to existing records. Make sure the trigger type matches the action you expect.
4. Conditions: Open the rule and review each condition. Are field names correct (including API names for custom fields)? Are picklist values case-sensitive matches? Is the operator appropriate for the field type?
5. Salesforce Object: The rule’s object must match the record type being created or updated. A rule on Opportunity will not fire when a Task is created.

Tip: Check the Ledger to see if entries are being created. If nothing appears, the rule conditions are likely not matching.

Novigem uses dedupe keys to prevent duplicate awards. However, there are cases where multiple entries are expected:

• Different rules, same record: If multiple rules match the same record update, each rule creates its own ledger entry. This is intended behavior.
• Recurring challenges: When a challenge period resets (weekly, monthly, quarterly), the dedupe key resets. The same record-rule combination can award points again in the new period.

To investigate, check the Rule__c field on each ledger entry. If different rules are firing, review whether you have overlapping conditions that should be consolidated.

The Actor Mode on the rule determines who receives points:

• Record Owner: The user in the OwnerId field
• Last Modified By: The user who made the edit
• Created By: The user who created the record

Common cause: A rule is set to Record Owner, but someone other than the owner updates the record. The owner gets the points, not the person who made the edit.

Fix: To reward the person performing the action, change the Actor Mode to Last Modified By.

Note that system-level updates (workflow rules, Process Builder, flows) set Last Modified By to the running user context, which may be an admin or integration user.

If a challenge shows no progress even though you expect rules to be firing:

1. Rule not linked: Open the challenge and check the Linked Rules section. The rule must be explicitly linked to the challenge. Creating a rule does not automatically associate it.
2. Date range: For Timebound challenges, rules only contribute to progress between the start and end dates. Activity outside this window is not counted.
3. Challenge not Active: Challenges in Draft, Paused, or Ended status do not track progress.

1. Page layout: Components must be added to Lightning pages via Lightning App Builder. See the Components Guide for placement instructions.
2. Permissions: Users need read access to Novigem custom objects (Challenge__c, Ledger_Entry__c, Challenge_Progress__c, Badge__c, Badge_Award__c). Check that the Novigem permission set is assigned.
3. Browser cache: After deploying new page layouts, users may need a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) to see updated components.

Leaderboards rank users by total points earned within the active challenge. If rankings seem wrong, check:

• Are all relevant rules linked to the challenge?
• Do some rules award more points than others? A rule awarding 10 points contributes more than one awarding 2.
• Is the user enrolled in the challenge?
• For Recurring challenges, rankings reset each period.

The isChanged operator only works with Update triggers. It compares old and new field values. Common issues:

• Wrong trigger type: If the rule uses a Create trigger, isChanged will never match because there are no old values to compare.
• Value format: Set the value to "true" (the field must have changed) or "false" (the field must not have changed).
• No actual change: If a user saves a record without modifying the field, isChanged returns false. This is expected behavior.