[4.2.x] Doc'd use of asgiref.sync adapters with sensitive variables.

Backport of 6087bc4e15e89d968396807f8485f4b5624c4f03 from main.

1 files changed, 14 insertions, 0 deletions

diff --git a/docs/topics/async.txt b/docs/topics/async.txt
index f4483501bd..65138eb2b5 100644
--- a/docs/topics/async.txt
+++ b/docs/topics/async.txt
@@ -338,3 +338,17 @@ trigger the thread safety checks:
 Rather, you should encapsulate all database access within a helper function
 that can be called with ``sync_to_async()`` without relying on the connection
 object in the calling code.
+
+Use with exception reporting filters
+------------------------------------
+
+.. warning::
+
+    Due to the machinery needed to cross the sync/async boundary,
+    ``sync_to_async()`` and ``async_to_sync()`` are **not** compatible with
+    :func:`~django.views.decorators.debug.sensitive_variables`, used to mask
+    local variables from exception reports.
+
+    If using these adapters with sensitive variables, ensure to audit exception
+    reporting, and consider implementing a :ref:`custom filter
+    <custom-error-reports>` if necessary.