Reject activities
Overview
Activity rejection allows administrators to reverse benefits earned from activities within 30 days of creation. This function helps maintain system integrity by addressing:
- Erroneous activity submissions
- Attempted system exploitation
- Data correction requirements
- User-requested activity cancellations
How to reject an activity
Activities can be rejected through:
- The User Portal - locate the activity and select "Reject Activity"
- The API - use the reject activity endpoint
Rejection process and consequences
When an activity is rejected, several changes occur automatically:
Activity changes
- The state property is set to "Rejected"
- All awarded rewards have their status set to "Rejected"
- Points from the activity are marked as rejected
- Coupons earned are marked as rejected
- For behaviour-based activities, all behaviours' status is set to "Rejected"
User impact
- Users lose behaviours, rewards, and prizes (points, coupons, tags) earned from the rejected activity
- The changes appear in the user's activity feed with a rejection message
Cascading effects
When rejecting an activity affects other achievements:
- If a user loses eligibility for rewards in other activities:
- Those rewards' status is set to "Rejected" in the impacted activities
- Associated points and coupons are also rejected
- If a user retains eligibility for rewards despite the rejection:
- The system automatically generates a new compensatory activity
- This new activity includes the remaining entitled rewards, points, and coupons
KPI handling
- New KPI information is added to the rejected activity showing the impact
- Current awarded KPI information remains unchanged in the system
- Any KPI-associated coupons are marked as rejected
Coupon handling
Coupon Buy Activities
Rejecting the "Buy" activity for Coupons with two step redemption mode causes the Coupon to be refunded. The Point "Redeem" transaction associated with the activity will be rejected, and its points will be returned to the Point Wallet's balance. For more information refer to the documentation on Coupon Refunds.
Coupon Redeem Activities
Rejecting a Coupon "Redeem" activity causes the Coupon to be refunded. The Point "Redeem" transaction associated with the Coupon Buy activity used to purchase the coupon will be rejected, and its points will be returned to the Point Wallet's balance. For more information refer to the documentation on Coupon Refunds.
Coupon Refund Activities
Rejecting a Coupon "Refund" activity has different effects depending on the configuration of the Coupon:
- Coupons that can not be bought with points: rejecting a "Refund" activity causes the Coupon to be redeemed once again.
- Coupons that can be bought with points:
- If the coupon has One-Step Redemption: rejecting a "Refund" activity causes the Coupon to be redeemed once again. If the user no longer has a sufficient point balance to redeem the Coupon, the "Refund" activity will be marked as rejected but the Coupon will not be redeemed.
- If the coupon has Two-Step Redemption: Rejecting a "Refund" activity is not allowed.
Limitations and important notes
- System-generated activities cannot be rejected
- Activities older than 30 days cannot be rejected
- KPI rejection may result in partial changes based on a user's current progress
- Parent IDs in points and coupons lists can be traced back to their origin (behaviours, rewards, KPIs)
Example scenarios
Scenario 1: Rejected activity with achievement (insufficient behaviours)
Situation: An activity with an achievement that awards prize points is rejected, and the user no longer has sufficient behaviours to maintain the achievement.
Outcome:
| Component | Change |
|---|---|
| Activity | State set to Rejected |
| Achievement | Status set to Rejected |
| Behaviour | Status set to Rejected |
| Points | Flagged as rejected |
User impact:
- Behaviour removed from profile
- Achievement removed from profile
- Points removed from profile
Scenario 2: Rejected activity with achievement (sufficient behaviours)
Situation: An activity with an achievement that awards prize points is rejected, but the user still has enough behaviours to maintain the achievement.
Outcome:
| Component | Change |
|---|---|
| Activity | State set to Rejected |
| Achievement | Status set to Rejected in this activity only |
| Behaviour | Status set to Rejected |
| Points | Flagged as rejected in this activity only |
User impact:
- Behaviour removed from profile
- Achievement retained in profile
- Points retained in profile
System action:
- Creates a new compensatory activity containing:
- The retained achievement
- Associated points
Scenario 3: Rejected behaviour activity affecting achievement in another activity
Situation: A behaviour activity is rejected, resulting in the user having insufficient behaviours to maintain an achievement with prize points that was unlocked in a different activity.
Outcome:
| Component | Change |
|---|---|
| Rejected Activity | State set to Rejected |
| Behaviour | Status set to Rejected |
| Related Activity | Achievement status set to Rejected |
| Points | Flagged as rejected in related activity |
User impact:
- Behaviour removed from profile
- Achievement removed from profile (due to insufficient behaviours)
- Points removed from profile (associated with the achievement)
Troubleshooting
| Issue | Solution |
|---|---|
| Activity not rejectable | Verify the activity is less than 30 days old and not system-generated |
| Unexpected user point balance | Check for compensatory activities that may have been created |
| Missing rejection history | View the activity logs section for full rejection details |