diff --git a/serverlessworkflow/modules/ROOT/pages/core/timeouts-support.adoc b/serverlessworkflow/modules/ROOT/pages/core/timeouts-support.adoc
index f1b32fda2..6933bef69 100644
--- a/serverlessworkflow/modules/ROOT/pages/core/timeouts-support.adoc
+++ b/serverlessworkflow/modules/ROOT/pages/core/timeouts-support.adoc
@@ -10,6 +10,11 @@ For example, you can configure how long a workflow can wait for an event to arri
 Regardless of its application scope (workflow or state), the timeouts must be configured as an amount of time (a duration), which is considered to start when the referred scope becomes active. Timeouts use the link:https://en.wikipedia.org/wiki/ISO_8601[`ISO 8601` data and time standard] to specify a duration of time and follow the format `PnDTnHnMn.nS` with days considered to be exactly 24 hours.
 For instance, `PT15M` configures 15 minutes, and `P2DT3H4M` defines 2 days, 3 hours and 4 minutes.
 
+[NOTE]
+====
+Month based timeouts like P2M (period of two months) are not valid since the month duration might vary. In that case you can use PT60D instead.
+====
+
 [#workflow-timeout]
 == Workflow timeout 
 To configure the maximum amount of time a workflow can be running before being canceled, you can use the workflow timeout.