Troubleshooting
Action results and routine performance
Classify the outcome, inspect evidence and avoid unsafe retries when one automation does not behave as expected.
Classify before fixing#
Swipe sideways to read all columns, or focus the table and use the arrow keys.
| What you see | Likely category |
|---|---|
| Feature or reward visibly absent | Game availability or prerequisite. |
| Queue already running | No action needed; configuration may be correct. |
| Expected menu never opened | Navigation, mapping or blocking-screen problem. |
| Menu opened but result is uncertain | Verification problem; inspect before retrying. |
| The entire run is slow | Environment capacity, game loading, repeated recovery or overly broad routine. |
| Only one workflow repeats | Workflow-specific state or unsupported variation. |
Why a routine can be slow#
- Game and emulator startup dominates a small routine.
- The routine contains many unavailable workflows that each require bounded checking.
- Recognised pop-ups or loading transitions require recovery time.
- The PC is memory constrained and emulator rendering is delayed.
- Several farms are competing under a concurrency setting that is too high.
- Evidence capture or a safety deadline is being reached repeatedly.
Safe investigation#
- 1
Note the exact farm, routine and action
Include the observed result and the outcome you expected.
- 2
Read the action outcome and duration
Find the first unexpected step, not merely the last line.
- 3
Open its evidence
Compare it with the actual game state.
- 4
Check prerequisites and settings
Confirm the task was available and intentionally enabled.
- 5
Retest narrowly
One farm, one relevant workflow, normal concurrency.
Do not blindly replay
If the action might have spent resources, claimed a one-time reward or dispatched troops, establish the current state before another attempt.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.