D1 diagram: reference, object and next step
Reference, object, outcome: keep the questions separate.

Trace a total to the right innings

When to use this route

A player’s public total disagrees with the card or another profile.

What to do, in order

  1. Open a known fixture and record competition, season, date, team and innings. Confirm the player as listed on the card; a common name or nickname is not a match.
  2. Follow the innings contributing to the profile total. Compare the same date range, match type and team on both views and count a rescheduled match only once.
  3. Mark the first missing or wrongly assigned innings and retain the profile and fixture references. If the underlying entry is wrong, send that entry to the organiser rather than requesting an aggregate change.

How to recognise the result

You can account for the total using the same match set, or name a particular innings that should be reviewed.

If it does not resolve

  • Do not divide runs by innings to compare batting averages if the records use dismissals. Check any not-outs and remove duplicate fixtures before recomputing.

Request help with duplicate profiles

When to use this route

Two profiles seem to describe one player, but neither your name nor a matching avatar proves that.

What to do, in order

  1. Keep the profile link for each record and one confirmed match card for each club. Compare names, team and innings before telling the organiser which match is yours.
  2. If the card lists the right player but links to the wrong profile, ask the organiser to identify the record they control. If the app’s published support channel is available from the observed listing, ask what evidence it accepts for the profile association.
  3. Once there is a response, open the original card again and check which profile it resolves to. Check the next affected card before treating aggregates as corrected.

How to recognise the result

The affected card resolves to the right player, or the responsible channel has the two exact records to reconcile.

If it does not resolve

  • No current self-service merge path was verified. Do not create a third profile or share verification codes to force a merge.

Separate account access from public stats

When to use this route

The card appears under the correct profile but you cannot open that profile from your handset.

What to do, in order

  1. Identify the app using its store record and compare the public card with what you can see while signed out. Save the exact point where account access fails.
  2. Use the recovery option shown inside the identified app if present. If it fails, use the publisher contact on the verified store listing and share the error and public profile reference, omitting credentials.
  3. After regaining access, confirm the original profile and a previous scorecard before assigning yourself to a new match.

How to recognise the result

You can recognise your existing record, or submit a reproducible access issue without losing the evidence needed to identify it.

If it does not resolve

  • A working public profile does not show that account recovery succeeded. No specific OTP provider, delivery time or fallback channel was confirmed.

READ THE SOURCE / CHECK THE DATE

Documents & references

Dates below belong to the historical references. The writing date does not represent a new account or file test.

  1. CricHeroes on Google Play: India listing2026-11-18 · play.google.com
  2. CricHeroes on the India App Store2026-11-18 · apps.apple.com

More on CricHeroes

D1 is an independent information publisher. Product providers handle their own accounts, files and transactions. How we write →