Troubleshooting & FAQ

General questions

Can I edit a deployed strategy?

No. Cancel the strategy first, make your changes, then redeploy. See Cancel or Stop a Strategy.

Does cancelling a strategy close my open positions?

No. Cancellation stops the strategy flow but leaves open positions intact. Close them manually from the trading interface or with a separate order.

Can I run the same strategy multiple times at once?

Yes. You can deploy the same strategy (or multiple strategies with identical logic) as separate instances. Each deployment is independent.

How many cycles can a strategy run?

The maximum is 10 cycles per strategy. If you need more, redeploy the strategy after it completes.

What happens if a node fails mid-flow?

The strategy stays Active but stops at the failed node. Open the strategy in canvas view mode to see which node failed and why. You may need to cancel and redeploy with a corrected configuration.

Can I test a strategy before deploying with real funds?

Use the canvas view and the built-in tutorial mode to trace through your strategy’s logic visually. There is no simulated or paper trading mode in the current version. You can use the chart to inspect price action and test indicator settings before committing.

Deployment issues

The Deploy button is grayed out.

Either your wallet is not connected or the strategy has unsaved changes. Save the strategy first using the toolbar, then connect your wallet. The Deploy button activates when both conditions are met.

“Indicator node has no conditions configured.”

An Indicator node in your strategy has no conditions set. Open the flagged node, add at least one condition, and try deploying again.

“Oracle registration failed.”

A custom data source used by your strategy could not be registered. Check that the external endpoint is reachable and returns the expected data format, then try deploying again.

The strategy deploys but immediately shows as Cancelled.

Synchronicity rejected the strategy. Common causes:

• An Order node references a market that is unavailable or in maintenance.
• Margin is too low to cover the position size you configured.
• A cycle configuration exceeds the maximum allowed (10 per edge).

Check each Order node’s margin and size settings, then redeploy.

Strategy not triggering

My strategy is Active but never fires.

This usually means the conditions in your Indicator have not been met yet. Open the strategy in canvas view. If the Indicator node is highlighted as the active node, the strategy is waiting, that’s expected.

If the conditions should have been met based on recent price action, check:

• The comparison operator is set correctly (greater than vs. less than, crossover vs. static threshold).
• The indicator period matches your intent. EMA(12) and EMA(24) on a 1-minute chart behave very differently from the same settings on a 1-hour chart.
• The combinator (AND/OR) is set the way you intended.

My limit order is not filling.

Limit orders fill only when the market reaches your specified price and liquidity is available at that level. If the price is close but the order still has not filled, the market may not have cleared at or through your limit price yet.

Exit not triggering

The position is open but the close Trigger never fires.

Check:

• The condition in the Trigger is correct. Open the strategy in canvas view and confirm the node is highlighted as active.
• The comparison direction. If you meant “close when RSI > 70” but configured “RSI < 70,” it will not fire during a rally.
• Whether the stop loss or take profit already closed the position. If so, the strategy may have moved past the Trigger.

The stop loss did not trigger.

A stop loss triggers when the market reaches your configured price. In fast-moving markets, the fill price may differ from the stop price when using a market order for the close. If using a limit stop, the order may not have filled if the market moved through the stop price without matching.

Import and export

Import fails with “Invalid JSON.”

The clipboard does not contain valid strategy JSON. Re-copy the exported strategy and try again. Make sure nothing was added or removed from the text after export.

After import, the strategy looks different from the original.

Node positions on the canvas may differ after import, but the configuration should be identical. If the logic itself looks different, check that the original export was not modified before importing.