Troubleshooting Gamification

Troubleshooting

Start with Cointacted → Gamification → System. Record the active plugin version, database status, Pro capability, registered activity sources, recent activity monitor rows, reward-ledger health, scheduled jobs, and migration state before changing anything.

A reward did not post

1. Confirm the rule is published, inside its schedule, and listening to the expected canonical event.
2. Check the Activity monitor for the event and resolved member.
3. Check rule conditions, limits, cooldowns, and the chosen point type.
4. Search the Reward ledger for the event's idempotency key or provenance hash.
5. Read the first recorded denial or error instead of replaying the event manually.

A duplicate event that produces no second reward is normally correct idempotent behavior. Create a separate manual award only when the business decision is genuinely separate and include its own reason.

Pro automation stopped

Verify the Gamification Pro capability in Cointacted → Add-ons. Existing paid configuration remaining visible while new paid mutations and listeners are blocked is the expected expiry behavior. Renew or reactivate access, refresh products, and allow the saved checkpoints to resume; do not recreate rules or provider mappings.

myCred or GamiPress is unavailable

Activate the provider and confirm it exposes at least one point type. Open the matching integration screen and run a dry preview. A paused run can be continued. Inspect per-record attempts for the first error. Provider deactivation pauses work without advancing the checkpoint.

If the provider changed a point-type identifier, stop and update the reviewed mapping. Do not create a random replacement mapping, because that can turn one economic unit into two unrelated currencies.

Balances differ

Run report-only current-balance reconciliation first. Compare the authoritative records, mapping direction, precision, opening balance, reversals, and the latest completed checkpoint. Investigate each conflict before enabling writes.

Reverse an incorrect Gamification transaction; never edit a posted ledger row. Use an opening balance only when source history is genuinely unavailable. If a decimal source maps to a whole-number Free point type, resolve the precision policy before importing.

A member page is empty or returns 404

Verify the destination toggle under Cointacted → Gamification → Display, signed-in state, selected point-type allow-list, section toggles, profile visibility, member opt-out, and the owning adapter's capability. A composed page contains only sections explicitly enabled by the administrator and preserves their saved order.

For a 404, save WordPress permalinks once after changing route configuration. Then test the direct URL before testing SnapWeb or FluentCommunity navigation. A native bridge should mount the same privacy-filtered presenter, not an empty duplicate renderer.

Safe support bundle

When requesting support, include plugin versions, the failing route or rule identifier, timestamps, the public system-health summary, and redacted error text. Never include license keys, connected-account tokens, wallet signatures, REST nonces, private ledger metadata, raw provider payloads, or database exports containing member data.