HTR Invest
Activity
Order blotter
Sign in to see your activity
Your orders, refusals and audit trail are private to your account.
Sign inWhy HTR did not trade
You have no account yet, so nothing has been refused on one. The reasons it could give are listed below.
Why a trade is refused
Every refusal the risk engine can return, each a declared constant rather than a message assembled at the point of failure — so the reason a reader sees is the reason the code acted on.
- R_ASSET_CLASS_OFFasset_class_disabled_by_user
- R_DAILY_LOSS_LIMITdaily_loss_limit_reached
- R_DAILY_TRADE_LIMITdaily_trade_limit_reached
- R_DRAWDOWN_LIMITportfolio_drawdown_limit_reached
- R_ENGINE_UNHEALTHYengine_unhealthy
- R_MARKET_CLOSEDmarket_closed
- R_NO_CONTEXTinsufficient_context
- R_POSITION_LIMITposition_limit_reached
- R_POSITION_TOO_LARGEposition_exceeds_max_size
- R_SHARIAH_FAILshariah_screen_failed
- R_SHARIAH_UNKNOWNshariah_verdict_unknown
- R_STALE_MARKET_DATAstale_market_data
- R_STALE_SHARIAH_DATAstale_shariah_data
- R_STRATEGY_UNAVAILABLEstrategy_not_offerable
- R_TRADING_HALTEDtrading_halted
What it must know first
The risk check fails closed: if any of these is missing it refuses rather than assuming a safe default.
Audit log
Every entry a live account writes is hash-chained: each row carries the previous row's hash, so a changed or deleted row breaks the chain and is detectable. That is tamper-EVIDENT, not tamper-proof, and the distinction is deliberate.
Paper and backtest results are hypothetical and do not represent actual trading. Past performance does not guarantee future results. Shariah screens and purification/Zakat figures are calculation aids, not religious rulings.