Code Review

Use a simple state machine to make EA behavior understandable.

A state machine prevents the EA from mixing setup detection, order execution, position management, and cooldown into one unreadable tick loop.

Search intent

The developer needs cleaner EA lifecycle control.

Short opt-in only. We store one source, one intent, and one new lead status. No scraped lists, no purchased contacts, no trading promises.

I agree to receive Workfusion EA builder updates and understand I can unsubscribe later.

Choose the workflow you want, then opt in so the CRM source is measurable.

Define lifecycle states

Keep the states simple and tied to actions the EA can explain.

Waiting

SignalDetected

RiskApproved

OrderSent

PositionOpen

Cooldown

Every transition should have a reason and a log entry. That makes stuck states easy to diagnose.

Signal true

Risk gate passed

Order accepted

Position closed

A state function should not secretly bypass risk checks or send orders without updating state.

One execution path

Explicit block paths

Consistent timestamps

Review your EA structure in Workfusion before adding more strategy branches.

Related guides

Compiler Fixes

MQL5 OnInit and OnTick EA skeleton

A clean MT5 Expert Advisor skeleton structure for OnInit, OnTick, risk gates, signal checks, and execution.

Code Review

MQL5 code review before backtesting

Review lifecycle, execution, risk, inputs, and logs before spending time on MT5 Strategy Tester runs.

MT4 Debugging

Debug an EA that opens too many trades

Find duplicate-entry, missing cooldown, magic number, and signal-state issues in an EA that overtrades.