diff --git a/docs/_articles/en/apex/replay-debugger.md b/docs/_articles/en/apex/replay-debugger.md
index 487d2732b9..4298c3534f 100644
--- a/docs/_articles/en/apex/replay-debugger.md
+++ b/docs/_articles/en/apex/replay-debugger.md
@@ -61,6 +61,7 @@ When you’ve stepped through all the logged events, the debugging session ends.
 
 Keep these considerations and known issues in mind when working with Apex Replay Debugger.
 
+- To hit all the breakpoints correctly when you launch the replay debugger from a log file, make sure that the `.cls` or `.trigger` file you used to generate the log is identical to the file with which you're working. 
 - You can use this debugger only in your orgs. ISV customer debugging is unavailable in Apex Replay Debugger. To debug customers’ orgs, use [ISV Customer Debugger](./en/apex/isv-debugger).
 - You can replay only one debug log at a time. This limitation can make it difficult to debug asynchronous Apex, which produces multiple debug logs.
 - Be sure to start a debugging session soon after uploading your checkpoints, because checkpoints expire after 30 minutes.