Found while doing #1117 (PR #1401). Filed rather than swept in: #1117's census proves the Stripe Sync line wrong and that one is fixed there, but the two neighbours on the same page are proven wrong by a different measurement and belong to their own card.
What is left
content/docs/reference/faq.mdx (and .zh-Hans / .zh-Hant), section 🔌 Integrations:
| line |
claim |
measured |
| ~150 |
"The Gmail / Outlook connector is connected (Settings → Email)" |
No connector, and no such screen. There is no Settings app; the only email surface that ships is outbound Send Email on a contact |
| ~156 |
"Check the DocuSign integration log (Setup → Integrations → DocuSign → Activity)" |
No DocuSign connector, therefore no log. Setup → Integrations is real, but it holds exactly two platform-contributed entries — Connect an Agent and Datasources — and no vendor mounts anything under it |
Zero occurrences of DocuSign in src/; zero connector metadata of any kind. This is not new information to the repo — content/docs/guides/integrations.mdx says it in its own words on the same docs set:
What it does not do yet is ship packaged vendor connectors — src/ carries no connector metadata of any kind, and nothing this app installs puts a connector under Setup → Integrations.
and lists both DocuSign and Gmail/Outlook in its (not shipped yet) table, with "Nothing" and "Send Email — outbound only" as the closest things that ship.
Why it survived
#756 is the parent defect ("guides/integrations.mdx lists 10 connector families as Built-in … the repo has no connector metadata"). It was fixed thoroughly — that page is now one of the most careful in the docs set, marking every unshipped section and explaining what is under Setup → Integrations. But the fix was scoped to the pages that list connectors. reference/faq troubleshoots them, in the imperative, and was never opened. A reader who hits the FAQ first is told to go check a log that has never existed.
Note the shape: neither line is a bold **App → …** citation, so #853's navigation guard cannot see either one, and neither can #1117's widening. Setup → Integrations → DocuSign → Activity sits in plain parentheses. This is rule 1 territory (a name the platform ships nowhere, no arrow required) if anything is to guard it at all.
Suggested shape
Rewrite the two answers the way #1401 rewrote the Stripe one: say what actually ships, point at Integrations, and drop the troubleshooting steps for a connector that cannot be misconfigured because it is not there. Three locales each. Worth checking the rest of reference/faq*.mdx for other #756 residue in the same pass.
Refs #756 (parent, closed) · #1117 / PR #1401 (where this surfaced) · #853 (the navigation guard, which cannot see these)
Found while doing #1117 (PR #1401). Filed rather than swept in: #1117's census proves the Stripe Sync line wrong and that one is fixed there, but the two neighbours on the same page are proven wrong by a different measurement and belong to their own card.
What is left
content/docs/reference/faq.mdx(and.zh-Hans/.zh-Hant), section 🔌 Integrations:Settingsapp; the only email surface that ships is outbound Send Email on a contactZero occurrences of
DocuSigninsrc/; zero connector metadata of any kind. This is not new information to the repo —content/docs/guides/integrations.mdxsays it in its own words on the same docs set:and lists both DocuSign and Gmail/Outlook in its (not shipped yet) table, with "Nothing" and "Send Email — outbound only" as the closest things that ship.
Why it survived
#756 is the parent defect ("guides/integrations.mdx lists 10 connector families as Built-in … the repo has no connector metadata"). It was fixed thoroughly — that page is now one of the most careful in the docs set, marking every unshipped section and explaining what is under
Setup → Integrations. But the fix was scoped to the pages that list connectors.reference/faqtroubleshoots them, in the imperative, and was never opened. A reader who hits the FAQ first is told to go check a log that has never existed.Note the shape: neither line is a bold
**App → …**citation, so #853's navigation guard cannot see either one, and neither can #1117's widening.Setup → Integrations → DocuSign → Activitysits in plain parentheses. This is rule 1 territory (a name the platform ships nowhere, no arrow required) if anything is to guard it at all.Suggested shape
Rewrite the two answers the way #1401 rewrote the Stripe one: say what actually ships, point at Integrations, and drop the troubleshooting steps for a connector that cannot be misconfigured because it is not there. Three locales each. Worth checking the rest of
reference/faq*.mdxfor other #756 residue in the same pass.Refs #756 (parent, closed) · #1117 / PR #1401 (where this surfaced) · #853 (the navigation guard, which cannot see these)