diff --git a/docs/dci-troubleshooting.md b/docs/dci-troubleshooting.md
index fc1d7a9..dad4564 100644
--- a/docs/dci-troubleshooting.md
+++ b/docs/dci-troubleshooting.md
@@ -148,6 +148,8 @@ The frontend sends two input tables with the startup service and with the servic
 
 The services that receive the tables are: `public/startupservice`, `editors/getdata`, `editors/getdynamiccolvals`, `editors/stagedata`, `editors/loadfile`, `editors/restore` and `auditors/postdata`.
 
+`editors/loadfile` is the exception in practice: the app reaches it through the adapter's file-upload call (multipart), which carries no input tables, so the service - and the post edit hook it runs - does not receive them in normal use. It is on the list for completeness, and would receive them if the service were ever invoked through the ordinary request path.
+
 ### browser_info
 
 A single-row table with these columns:
@@ -179,7 +181,7 @@ Parameters from both the search string and the hash query string (Angular routes
 
 The values in both tables are supplied by the client, so treat them as diagnostics hints rather than a security boundary.
 
-To see the tables, run any of the services above with debug on (for example add `&_debug=131` to the service URL). The session initialisation then writes them to the job log:
+To see the tables, run any of the services above with debug on. The debug value depends on the path: `&_debug=131` on the Compute API and SAS 9, or `&_debug=128` on the Viya web (JES) path with `runAsTask` enabled - which is what the frontend sends there, so turning debug on in the app is enough. Either value makes the session initialisation write the tables to the job log:
 
 ```
 NOTE: MPEINIT: work.browser_url_vars: