---
title: "Discussion on \"The request.security() Value That Isn't There Yet\" | Hashnode"
description: "Discussion on \"The request.security() Value That Isn't There Yet\". \"Profitable in the Strategy Tester, losing money live\" usually gets blamed on slippage. One specific, mechanically checkable cause is worth ruling out first — and it's documented behavior, not a rare"
url: "https://hashnode.com/posts/request-security-value-that-isnt-there-yet/6a9302830ae17790ca557300"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The request.security() Value That Isn't There Yet](https://honest-backtest.hashnode.dev/request-security-value-that-isnt-there-yet?utm_source=hashnode&utm_medium=feed)

"Profitable in the Strategy Tester, losing money live" usually gets blamed on slippage. One specific, mechanically checkable cause is worth ruling out first — and it's documented behavior, not a rare

Aug 29 · 5 min read · honest-backtest.hashnode.dev  
Read the article

-   [#pinescript](https://hashnode.com/tag/pinescript)
-   [#trading](https://hashnode.com/tag/trading)

## Written by

[Valerii Sakara](https://hashnode.com/@arakas4488cmd)

@arakas4488cmd

  
[View profile](https://hashnode.com/@arakas4488cmd)

Independent code audits for algorithmic trading bots — real bugs, real backtests, no marketing curves.

I audit algorithmic trading bot code for a living — entry/exit logic, order management, risk handling, fee-honest backtests. I've filed 40+ public responsible-disclosure issues against live open-source trading bots, and audited my own bot the same way before offering this to anyone else.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.