SYMPTOM → CAUSE → FIX

Troubleshooting

Start at the failing step. Verify the target, input and real result in that order.

The workflow will not start

Check the selected group, unsaved draft, enabled state and entry group. An individual test, selected group and Full flow have different scopes. Read the first relevant error in the log.

Window not found

Refresh the target list. Launch the application if closed. A saved temporary HWND/PID can become invalid after reopening; consider a process-based match. If several windows share that process, identify the correct one.

The mouse goes to the wrong place

Distinguish screen and client coordinates. Check window size, DPI and geometry references. If using a located target, verify that the preceding search succeeded. Disable random offsets while diagnosing.

Keys or text do not arrive

Check focus and the destination field first, then foreground/background mode. Do not use unsupported Hold or combinations in background mode. Pair persistent key-down input with key-up and observe the application result.

Image missing or wrong match

Inspect the preview box and score. Recrop at the correct scale, narrow the region and exclude changing backgrounds. Lowering a threshold can increase false matches. Consider object tracking for moving targets.

OCR reads incorrectly

Crop closer and compare scale, inversion and language settings. Enlarging the image does not always help. Inspect the text before conversion. For coordinates, try separate X/Y regions.

Direction arrow is ambiguous

Reselect the arrow region, exclude same-colored map marks and inspect the learned shape/reference direction. A rotating map may invalidate a fixed north-up assumption. Avoiding movement without reliable heading is an intentional protection.

Progress could not be verified

Inspect current/target position, arrow/OCR age and input in the log. Check axes, turning keys, map visibility and obstacles. Try a nearby target and add waypoints where needed. A larger timeout does not fix an incorrect heading or a wall.

Formula error

Distinguish an undefined variable, type mismatch and division failure. Use a decimal point, quote text and produce variables before reading them. IFERROR can provide a deliberate fallback but should not conceal the underlying problem.

Export is unavailable

Check the Pro file-transfer right and refresh account rights. MCP access alone is not enough. Include the exact error and reproduction steps in support; never include the access key.

MCP sees an old workflow

Distinguish a cloud revision from the connected device’s open-project snapshot. Verify the device, project and timestamp. A queued delivery does not prove local loading or execution.

Useful support information

Provide the application version, module, expected/actual behavior, reproduction steps and sanitized logs/screenshots. Never send full passwords, API keys or MCP credentials.

Next stepBuild a workflow with these modules ↗Resolve a problem ↗