If something goes wrong
This page collects common situations and what to do about them. Find the section for your task and what you see on the screen.
Connection
| What you see |
What to do |
| There is no Connect AI agent menu item |
Check your ATAS version |
| A chat is open in the browser |
It won't connect to ATAS. Install the agent's desktop app |
| The web version of ATAS is open |
The connection works only in the ATAS and ATAS X desktop apps |
| The ATAS window waits a long time for a connection |
Check that the agent is open in its app on the same computer |
| The agent asked for a restart |
Restart it and send the connection prompt again |
| The agent says it doesn't know about ATAS |
The server is not connected. Go back to Connect and set up and restart the agent |
| Connection error |
Check that ATAS is running and the server is on in the Connect AI agent window |
| The agent doesn't connect after ATAS restarts |
The address may have changed if the old port was taken. Copy the prompt from the connection window and send it again |
| The token showed up in a screenshot or someone else got it |
Click Regenerate token. All agents disconnect, and you will need to connect them again |
Permissions
| What you see |
What to do |
permission_denied or a refusal for a function |
The agent names the permission. Turn it on in the Access tab and repeat the request |
| The agent asks for confirmation on ATAS functions |
This is a setting of the agent itself. Allow it to call ATAS functions |
| Orders are not sent |
Trading operations are off by default, or the trading lock is on: it applies to the whole platform |
| The agent says there is no market data for the instrument |
The agent gets quotes, bars, indicator values and chart screenshots for crypto. For futures and stocks, ask it to set up a chart or an indicator, and run calculations on data on a crypto instrument. More on the Security and data page |
The agent's answer
The agent can misread a chart, miscount or confidently present a guess as a fact. It can also quietly narrow the task: keep only one session because of something said earlier in the chat, or take data from an external service you have connected. So ask which data it used and what it filtered out.
| What you see |
What to do |
| Conclusions without numbers |
Write: "Give a time and a number for each claim" |
| A confident answer, but it's unclear where it comes from |
Ask which ATAS functions it called and what data it read. Without ATAS it writes from memory |
| The agent names a pattern without numbers |
Ask which numeric condition it checked |
| General advice instead of work with your numbers |
Ask: "Read my charts first and name the levels" |
| Statistics calculated right in the chat |
You can't trust that math. Write: "Calculate it with code" |
| The result looks too good |
Send Double-check the report and see what was filtered out |
| Answers differ from run to run |
The agent decides on its own what counts as important. You need a fixed criterion: state it as a number, "volume more than 5 times the average" |
| The menu items it names aren't in the interface |
The agent may be wrong or may have used an outdated article. Describe what you see on the screen and attach a screenshot |
| Labels in a different language |
The agent uses the ATAS interface language. Ask it to answer in the language you need |
| The agent couldn't find an answer about the platform |
Check whether it has web search. Phrase the question in terms of what you want to see on the screen |
Charts and markup
| What you see |
What to do |
| The agent changed too much or started changing things right away |
Put it back. Next time add: "don't do anything yet" |
| Labels overlap |
Ask it to shorten the labels, keep only the ones you need or scroll the chart to the right place |
| Labels are hard to read |
Ask it to change the color |
| After a background change, indicator labels are unreadable |
The indicator colors may have stayed the same. Ask it to change them too |
| Colors on your monitor are less readable than the agent promised |
Say what to adjust. The agent can't judge how the chart looks on your monitor |
| Extra indicators came with the template |
Ask it to save the template again with colors only |
| The profile on the chart is doubled |
A new chart may have come with a profile from the default template. Ask: "Keep one profile, the daily one" |
| A simulator position shows on the chart |
The agent didn't open it. You can hide it in the chart settings |
| Remove markup |
"Remove the markup". Lines and price alerts are undone; ask separately to delete a condition alert |
An alert only notifies you about the price. It doesn't place orders.
Trade review
| What you see |
What to do |
| No trades for the period |
The journal shows the limits of its history. Ask it to use the whole journal or a different period |
| The days don't match yours |
Name your time zone |
| The total differs from yours |
Ask whether commission is included and which accounts and entries went in |
| No breakdown by instrument |
The instrument field in the journal may be empty. The agent should not guess the instrument from the price |
| Entries without a close |
Ask how many such entries there are and whether they were excluded |
| The conclusion sounds too confident |
Ask how many trades are in that group. One trade doesn't mean anything yet |
Indicators
The script runs inside ATAS. Try a new indicator on a separate chart first, away from your trading.
| What you see |
What to do |
| Too many marks or none |
Ask it to show the distribution and refine the condition. Don't tune it to get a pretty picture |
| The threshold doesn't fit another day |
The threshold was picked for a specific day. Ask: "Test this threshold over the last week" or ask it to pick a threshold for the daily average |
| A mark appears and disappears |
Ask whether the indicator calculates inside an unclosed bar. Ask it to use closed bars only |
| The agent says behavior on live ticks hasn't been checked |
Leave the indicator on a separate chart for a session and watch whether marks appear and disappear. Tell the agent what you saw |
| Odd indicator name |
Ask it to rename it |
| The panel is small |
Ask it to make the panel taller |
| You don't need the indicator |
"Remove the indicator" takes it off the chart. The script stays in Script Lab; ask separately to delete it |
| Error on data from another time frame or instrument |
ATAS Script doesn't take such parts directly. Pick the option the agent suggested and ask what changes with it (example) |
| The result differs from the original |
Give the agent a few values from the source platform: date, time, value. It compares them and finds the cause (example) |
| The agent has doubts about rights to the code |
Check the license of the source. If there is none and the code isn't yours, ask the author |
| An edit broke something else |
"Go back to the previous version of the script": source code changes also go into the undo log |
Skills
| What you see |
What to do |
| The skill wasn't saved |
Paste its text at the start of the chat. The agent follows it in this conversation; in the next chat you need to paste the text again |
| Two skills fit |
For example, the built-in Day Map gives the question of the day and scenarios, and premarket gives a summary by level. Name the one you need in your request |
Undo
| What you see |
What to do |
| A setting didn't come back |
If you changed it by hand after the agent, it stays yours |
| Nothing to undo after ATAS restarts |
The log lasts until a restart. Restore the settings by hand |
| More was undone than you wanted |
You can't bring back what was undone. Ask the agent to do it again, or be more specific: "undo only the last change" |
If the answer isn't here
Tell the agent what you see and attach a screenshot: How do I do this in ATAS. The agent's requests are shown on the Log tab of the AI agent connection (MCP) window.