Skip to content

# Troubleshooting ​

Common issues and what to do about them.

## Sessions Are Not Opening ​

What you see: The countdown passes zero but the session stays PENDING.

What to check:

1. Is the engine active? Look at the status badge in the top right of the dashboard. If it says INACTIVE, sessions will not open. Contact your developer to activate the engine.
2. Is Emergency Pause on? Check the top of the Controls page. If the toggle is ON, turn it off.
3. Is a previous session stuck? Check Session History. If a session shows ACTIVE or PROCESSING for an unusually long time, contact your developer.

## All Bots Are Showing COLD ​

What you see: Every bot on the Bots page is red (COLD).

Before launch: This is expected. The governance system calculates what it would do but does not apply changes until the engine is active. All bots will appear behind target. This resolves automatically at go-live.

After launch: If all bots remain COLD after several days of the engine being active:

1. Check the plan ranges on the Controls page. Are the monthly targets realistic?
2. Look at the Audit Log for sell_evaluated events. If there are none, the engine may not be processing trades.
3. Contact your developer with what you see.

## Users Complaining About Rejected Sells ​

What to tell them: "Sell evaluations are competitive. Not every sell is approved in every cycle. Try adjusting your settings and submitting again. Visit manual.ge-as.com for tips on improving your results."

What to check on your end:

1. Look up the user on the Users page. Check their cap usage.
2. If cap usage is at 100%, their sells are on hold until next month. Tell them: "Your trading limit for this month has been reached. It resets on the 1st."
3. If cap usage is low, the sell was simply not selected this cycle. This is normal.
4. For persistent complaints, filter the Audit Log by the user's ID to see the specific evaluation details.

## A Bot Is About to Expire While COLD ​

What you see: The Settlement Pipeline shows a bot with 1 to 2 days remaining, COLD status, and clearly not going to reach its target.

What to do: Contact your developer. They have tools to adjust the bot's final settlement value so the user receives a return within the plan's stated range. The Bots page will show an alert when an adjustment has been made.

## You Changed a Setting and Something Went Wrong ​

1. Go to the Audit Log page.
2. Filter by event: CONFIG_CHANGED.
3. Find your recent change. Click VIEW to see the old value.
4. Go back to Controls and set it back to the old value.
5. Click SAVE.

If the issue persists after reverting, use Emergency Pause and contact your developer.

## Common User Questions and Your Answers ​

User Says | What It Means | Your Response
--- | --- | ---
"My sell was rejected" | Normal competitive evaluation | "Sell evaluations are competitive. Adjust your settings and try again. Check the trading guide at manual.ge-as.com."
"I cannot place a bid" | Session is not active | "Bidding is only available during trading sessions. Check the countdown on the product page for the next session."
"My AI plan earned nothing today" | Zero-profit day | "Some days the AI does not generate profit. This is normal. Your plan targets a monthly return, not a daily one."
"My sells keep failing" | Monthly limit reached or repeated non-selection | "Check if your monthly limit has been reached (it resets on the 1st). If not, try lowering your margin or widening your Recess. If that does not help, try pricing within the buyback margin for a guaranteed sale."
"Something is wrong with my account" | Unknown issue | "Please share your username and I will look into it." Then check their profile in the Users page and their history in the Audit Log.

## When to Contact Your Developer ​

- The engine is not starting sessions and you have checked Emergency Pause.
- A bot needs a profit adjustment before settlement.
- You want to change the Engine Status (activate or deactivate).
- A session appears stuck in ACTIVE or PROCESSING for more than 2 hours.
- You see errors or unexpected behaviour that the dashboard does not explain.

Your developer can access server logs and engine internals that are not visible from the dashboard.