The answer is too broad or generic
Usually a sign the prompt was too broad. Name what you care about, ask for specific drivers, metrics, and risks, and iterate in the same conversation rather than starting over:A financial figure looks wrong or missing
Ask the Agent to cite its sources and flag gaps. If it could not retrieve something, a good prompt makes it say so rather than guessing:A Skill ran that I didn’t expect
Driven routes to a Skill based on your prompt’s intent. To get a different one, rephrase to signal the intent more clearly, or name the Skill explicitly:A scheduled task didn’t run or produced nothing
A few common causes:- No time zone — an ambiguous time can misfire. Anchor it (“8 AM New York time”).
- Thresholds not met — a monitor set to alert only on certain conditions stays quiet when nothing crosses them. That is working as intended.
- Scope too narrow or too broad — review the task prompt and adjust.
A paper limit order is stuck
The Agent can see order IDs and cancel a pending order directly by ticker, so you do not need to go into the UI:A paper trade was rejected
Paper trading coverage can be narrower than research coverage. Confirm the market and asset type are supported for trading before relying on a workflow:The page or a browser extension is causing problems
If a browser translation extension interferes with the web app, try disabling it for the Driven site. If issues persist, contact support with your browser and extension details.A message or approval went missing on Telegram or WeChat
If you are not receiving expected messages or approvals on a messaging channel, confirm the channel is connected and check the web app, which always has the full record. Contact support if messages continue to go missing.Related
- FAQ — common questions
- Prompt library — getting better results
- Scheduled tasks — task configuration
- Skill routing logic — how Skills are selected