diff --git a/docs/source/reference/bentoml/configurations.rst b/docs/source/reference/bentoml/configurations.rst
index 548ee861064..02b8b452d6c 100644
--- a/docs/source/reference/bentoml/configurations.rst
+++ b/docs/source/reference/bentoml/configurations.rst
@@ -133,6 +133,8 @@ For more information, see :doc:`/build-with-bentoml/runtime-environment`.
     class MyService:
         # Service implementation
 
+.. _config-traffic:
+
 ``traffic``
 ^^^^^^^^^^^
 
diff --git a/docs/source/scale-with-bentocloud/scaling/autoscaling.rst b/docs/source/scale-with-bentocloud/scaling/autoscaling.rst
index 1085af453ba..6b4f0fe6200 100644
--- a/docs/source/scale-with-bentocloud/scaling/autoscaling.rst
+++ b/docs/source/scale-with-bentocloud/scaling/autoscaling.rst
@@ -88,7 +88,7 @@ You can enhance concurrency management with an external request queue on BentoCl
 
     If you enable ``external_queue`` in the ``@bentoml.service`` decorator, you must specify a ``concurrency`` value.
 
-It's worth noting that when the external queue is enabled, ``max_concurrency`` will no longer take effect because BentoCloud guarantees the Service will never receive more requests simultaneously than the ``concurrency`` setting allows. Therefore, ``max_concurrency`` is never reached.
+It's worth noting that when the external queue is enabled, ``max_concurrency`` will no longer take effect because BentoCloud guarantees the Service will never receive more requests simultaneously than the ``concurrency`` setting allows. Therefore, ``max_concurrency`` is never reached. For more information, see available fields in :ref:`config-traffic`.
 
 Autoscaling policies
 --------------------