docs(audiences): clarify first Salesforce export does not run immediately

[george-dilthey]

What changed

Clarified in two places in docs/audiences.md that the first Audiences→Salesforce export does not run immediately after enabling the Export sync toggle — it fires at the workspace's next scheduled export time, which may be up to 24 hours away.

Changed in two locations:

1. The "First export" bullet in the Export sync behavior list in the Writing back to your CRM section (line 448)
2. The last sentence of the existing FAQ: "I've mapped fields to Salesforce but the data isn't syncing — why?" (line 613)

Before (both locations): "the first export fires at your workspace's next scheduled export time — this may take up to 24 hours"

After (both locations): "the first export does not run immediately — it fires at your workspace's next scheduled export time, which may be up to 24 hours away"

Why

Intercom conversation #215475130065193 (Saviynt, Enterprise): Gabriel Griffith had configured Salesforce Account field mappings with "Always write" rules but wasn't seeing data sync. Human agent Peter Johnston explained: (1) the Export sync toggle must be enabled as a master switch, and (2) the first sync does NOT happen immediately — it's queued for the next scheduled 24-hour window.

The first point was already well-covered in the doc (including the existing FAQ entry that exactly matched the customer's question). The second point was present but ambiguously worded — "may take up to 24 hours" doesn't clearly exclude the possibility of near-immediate syncing (e.g., "maybe it syncs in 5 minutes"). The customer explicitly followed up: "should this happen immediately or is it queued up for the 24 hour window?" — and the agent answered: "the export gets triggered to occur within the next 24 hour window rather than immediately." This PR adds the explicit "does not run immediately" language that directly answers that follow-up question.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475130065193
• Verifier PASS (claim 1 — master switch): services/audiences/src/materialization/services/export-handler.ts:3470 — toggle check fires before field-level rules are evaluated
• Verifier PASS (claim 2 — first export not immediate): services/scheduler/src/bull/queues/audience-export-queue.ts — scheduleAudienceExportJob uses immediate: false; each workspace gets a stable daily cron slot (hash-derived). Comment in code: "Export runs on a fixed 24h cycle at the workspace's assigned slot. Enabling the toggle does not trigger an out-of-cycle run."
• Slack confirmation (Audiences engineer Alex Xu, #team-audiences, 2026-07-17): "it queues it for the next window. for every export, we assign an arbitrary time during the day."

Uncertainties

None. Both changes confirmed PASS by verifier with code + Slack evidence.

Related observations

• PR docs(audiences): add Export sync toggle prerequisite for Salesforce write-back #1615 (open) adds new setup prose + a new FAQ "My field mappings are set to 'Always write' but data isn't syncing..." — that new FAQ entry also uses the ambiguous "this may take up to 24 hours" phrasing, not "does not run immediately." After both PRs merge, reviewers may wish to align the timing language across the two FAQ entries.
• PR docs(audiences): document field-level write rules for Salesforce export #1617 (open) adds field-level write rule documentation (a table of Never write / Always write / Write if empty) — unrelated to this change.
• PRs docs(audiences): document signal detection-layer model and Data Hub vs. table scope #1605, docs(audiences): document archived record behavior on source re-sync #1587, docs(audiences): add read-only Salesforce field types and cross-object enrichment FAQ #1585, docs(audiences): add errored-row run-condition fix, delete-row note, and field-deletion FAQ #1582, docs(audiences): document Intelligence tab on company records (beta) #1569, docs(audiences): document nested sub-field mapping in bulk enrichments #1558, docs(audiences): add CSV export workaround via Add to workbook #1550, docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547, docs(audiences): document Salesforce custom object export limitation and workaround #1528, docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507, docs(audiences): add Databricks as beta import source #1485 are open on this file covering unrelated topics.

Closes DOC-1225

[linear-code]

DOC-1225