---
title: "Comment by Arnold Holm on \"5 Things I Check Before Debugging an MQL5 Program\" | Hashnode"
description: "For an EA that compiles, I start with one expected decision and the log from that exact tick. I want the symbol, bar time, inputs, open position and trade retur"
url: "https://hashnode.com/posts/5-things-i-check-before-debugging-an-mql5-program/6ac9ba3afe6b72a3e60ca95a/comment/6aca407a6e2159d6a6b1422a"
---

[Discussion](https://hashnode.com/posts/5-things-i-check-before-debugging-an-mql5-program/6ac9ba3afe6b72a3e60ca95a)

Comment [5 Things I Check Before Debugging an MQL5 Program](https://hashnode.com/posts/5-things-i-check-before-debugging-an-mql5-program/6ac9ba3afe6b72a3e60ca95a)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 10](https://hashnode.com/posts/5-things-i-check-before-debugging-an-mql5-program/6ac9ba3afe6b72a3e60ca95a/comment/6aca407a6e2159d6a6b1422a)

For an EA that compiles, I start with one expected decision and the log from that exact tick. I want the symbol, bar time, inputs, open position and trade return code in the same record. A successful function call alone does not explain whether the trade server accepted the request. Which of those fields do you keep in your first debugging log?
