diff --git a/articles/azure-functions/durable-functions-eternal-orchestrations.md b/articles/azure-functions/durable-functions-eternal-orchestrations.md
index a6aaff1fb4241..20aa89efa9d65 100644
--- a/articles/azure-functions/durable-functions-eternal-orchestrations.md
+++ b/articles/azure-functions/durable-functions-eternal-orchestrations.md
@@ -33,6 +33,10 @@ When `ContinueAsNew` is called, the instance enqueues a message to itself before
 > [!NOTE]
 > The Durable Task Framework maintains the same instance ID but internally creates a new *execution ID* for the orchestrator function that gets reset by `ContinueAsNew`. This execution ID is generally not exposed externally, but it may be useful to know about when debugging orchestration execution.
 
+> [!WARNING]
+> Current implementation of Durable Functions might ignore some calls to `ContinueAsNew` if done in a rapid succession. Be
+> careful in the use of this pattern at the moment.
+
 ## Periodic work example
 
 One use case for eternal orchestrations is code that needs to do periodic work indefinitely.