Good troubleshooting narrows the problem before changing the setup. A short sequence of checks can turn an unexpected result into a specific question you can answer.
Start with the intended rule
Find the automation and read its saved mode, amount rule, timing where applicable, withdrawal settings and end condition. Compare them with the behavior you expected. Use the saved configuration rather than memory.
Check the connection
Review the individual verification checks. Note exactly which check failed or needs attention. Avoid replacing credentials merely because an unrelated automation result looks wrong.
Follow the evidence
Open Logs for the relevant time and identifiers, then Transactions for recorded results. Review filters before deciding that data is missing. A skipped action, a failed operation and a completed conversion are different events.
Make one relevant change
Correct the setting or setup identified by the evidence. Then inspect the saved state. Repeated changes to several fields at once make the outcome harder to explain.
Escalate clearly
If the issue remains, contact support with the automation identifier, error text, approximate time and intended result. Exclude passwords, keys and authentication codes. The Knowledge Base guides can help you collect this context screen by screen.