Get help with installation, connection, Engineering Runs, audits, previews and engineering jobs.
Get help with OAuth, permission errors, reconnects and uninstall behavior.
Include the store domain and exact state without sending credentials.
Report clarification loops, blocked execution, failed QA or missing previews with the job reference.
Describe the expected result and the last successful state so support can reproduce the issue.
Ask about plan capacity, reservations, consumption, top-ups or payment state.
The product should preserve enough history to explain how a balance changed.
Use staging links and representative pages when reporting a visual or functional regression.
Include device, browser, template, steps and screenshots where safe.
Potential vulnerabilities follow the security reporting path.
Do not include tokens, passwords, customer data or exploit details in a public channel.
Unsupported architecture and consulting requests can move to senior engineering.
Support should explain the boundary and preserve existing context for handoff.
Related TaskerArmy pages
Connect the store. Start with evidence.
Connect your store, review the audit and choose the first change you want TaskerArmy to prepare in staging.