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

Open the exact match and innings

When to use this route

You know the teams or competition and want the live score or the completed result.

What to do, in order

  1. Find the event by competition and date. Match the team names and stage, then confirm whether the app labels the match scheduled, live, interrupted or complete.
  2. Open the innings in progress or the completed innings you want. Note which team is batting, runs, wickets and the over/delivery reference before switching views.
  3. Read the last available commentary item. If it’s a chase, verify the target and available overs in the same card before interpreting the required rate.

How to recognise the result

You can identify the fixture, innings and last recorded event, or the reason a live event is not showing.

If it does not resolve

  • A past match with the same teams or a different format can match the names and still be the wrong card. If the fixture is absent, check the organiser’s schedule before assuming a phone fault.

Compare two feeds at the same state

When to use this route

Your alert, the app and a second score feed display different totals or wickets.

What to do, in order

  1. Take a short record of each view: match, innings, batting side, last listed event and the time you checked. Use the latest ball within the same match, not the timestamp on a forwarded screenshot.
  2. If the delivery number matches, inspect extras and a possible review. If the delivery number differs, compare the earlier point first; one feed may not have recorded the new ball.
  3. For a rain interruption, check whether the revised target and match status have been confirmed. Revisit the scorecard and then the organiser’s published outcome if the result is still disputed.

How to recognise the result

The discrepancy resolves to the fixture, an event within the innings, an incomplete update or an unresolved match status.

If it does not resolve

  • Do not substitute a win projection for a result or treat a feed disagreement as proof of an official correction. Keep both references if they have not converged.

Tell delayed coverage from a stale local view

When to use this route

A covered match has a static card but another view is moving.

What to do, in order

  1. Confirm that the match is active and try reopening its card once. Check whether another active match loads normally on the same connection.
  2. Compare the affected fixture on a second connection or another published score view. Record the first event that differs and whether the rest of the app updates.
  3. Use the official competition result for a final decision. If you need to report a feed issue, provide the match and missing interval with your device and app version.

How to recognise the result

You can isolate a single fixture feed, a local connection issue or a match interruption.

If it does not resolve

  • If the card updates but no notification arrived, use the alert checks on the device; a reinstall is not the first comparison.

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. Cricket Guru on Google Play: India listing2026-11-18 · play.google.com
  2. Cricket Guru on the India App Store2026-11-18 · apps.apple.com
  3. Cricket Guru: publisher’s public product page2026-11-18 · www.cricketguru.com

More on Cricket Guru

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