Core concepts
Results, statuses and evidence
Interpret completed, skipped, unavailable, failed and operator-attention outcomes before retrying a farm.
Outcome meanings#
Final labels may be refined before release, but the distinction between success, no work, game unavailability and software failure is fundamental.
| Outcome family | Meaning | Next step |
|---|---|---|
| Completed | The intended terminal change was verified. | Continue normally. |
| No action needed | The farm was already in an acceptable state. | Review only if unexpected. |
| Unavailable in game | The feature, event, queue, item or prerequisite was not available. | Change game state or wait. |
| Skipped by configuration | Your routine or limit intentionally excluded the action. | Review settings if needed. |
| Failed | The action could not reach or prove a safe outcome. | Inspect evidence before retrying. |
| Needs operator attention | The current screen or result is too uncertain for automatic recovery. | Open the emulator and resolve visibly. |
What evidence is for#
Evidence is a customer-facing record of the screen or state around a result. It helps distinguish a locked feature from a navigation failure, or a completed reward from a menu that merely closed.
Evidence may contain visible in-game names or account state. Review it before sharing and send it only through the official support path.
Decide whether to retry#
- Safe to retry: a read-only opening step failed before any possible spend, dispatch or claim, and the current game state is known.
- Wait instead: the queue is active, an event is unavailable, a cooldown is visible or the emulator is still loading.
- Inspect first: a reward may have been claimed, resources may have been spent or troops may have departed.
- Do not retry repeatedly: the same uncertain result recurs without a clear change in screen or configuration.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.