Questionnaire Hidden Variable Data Loss

SELECT id, source, is_completed, critical_update, created, modified
FROM `spotdraft-prod.prod_usa_db.public_contracts_v3_contractdata`
WHERE contract_id = {contract_id}
ORDER BY created DESC
LIMIT 10

Look for the pattern:

• source: Info-Collection, is_completed: False, critical_update: True — values present (initial HubSpot push)
• source: partial-save or source: Info-Collection with is_completed: True — values absent/zeroed (result of questionnaire edit)

Check contract state (Prod US):

SELECT id, status, contract_kind, workflow_status, created, modified
FROM `spotdraft-prod.prod_usa_db.public_contracts_v3_contractv3`
WHERE id = {contract_id}

Check contract version history:

SELECT id, version_number, sub_version_number, action, is_current, created
FROM `spotdraft-prod.prod_usa_db.public_contracts_v3_contractversion`
WHERE contract_id = {contract_id}
ORDER BY version_number DESC, sub_version_number DESC
LIMIT 10

⚠️ Run BQ queries one at a time — parallel execute_sql calls return 500 errors.

Environment-to-Dataset Mapping

GCP Cloud Logging — Questionnaire Edit Activity

Search for questionnaire save events for a contract (Prod US):

logName="projects/spotdraft-prod/logs/stderr"
resource.labels.cluster_name="prod-usa"
jsonPayload.message:"{contract_id}"
severity >= ERROR

QA equivalent:

resource.type="k8s_container" labels."k8s-pod/app"="spotdraft-qa-django-app"
textPayload:("{contract_id}") textPayload:("questionnaire" OR "question_item" OR "contract_data")

Admin Panel URLs

When to Use This Skill

Use when:

• Customer reports integration-sourced field values (HubSpot/Salesforce) missing from a contract that was created via a template workflow
• Customer says "fields that used to show correct values now show 0 / are blank"
• Issue appears after the customer or SpotDraft team edited the contract questionnaire
• Customer is on a workflow where implementation hid certain fields from the UI using a dummy condition variable (commonly sd_show)
• Customer reports the issue started around March 4–17, 2026, or after any deployment that changed questionnaire visibility behavior

Do not use for:

• Integration connection errors (HubSpot/Salesforce not syncing at all)
• Contract PDF generation issues
• Email or signing workflow failures

Platform Behavior: The Root Cause

Normal flow (working correctly)

1. Contract created via HubSpot/Salesforce integration → integration pushes variable values directly into ContractData
2. The initial data push bypasses questionnaire visibility rules (it writes to variables, not question items)
3. Fields appear correctly in the contract document

Break point: questionnaire edit on SpotDraft

When a user edits the questionnaire via the SpotDraft UI (or when the platform re-evaluates it):

1. The visibility rule engine evaluates each question's condition_as_json_logic or condition_as_complex_expression
2. Questions that evaluate as hidden have their values cleared and not written back to ContractData
3. Result: integration-sourced values are wiped, replaced with defaults (often 0 or empty)

The always-false hidden question pattern (workaround used by Legal Ops)

Implementation teams sometimes hide integration-mapped questions from the UI by placing them behind a condition that always evaluates to false — typically a dummy variable like sd_show (which has no questionnaire field and no default, so it is never set to true). This achieves the goal of hiding the field from sellers, but creates a data-loss risk on any questionnaire edit.

Technical form of the condition:

• Simple: condition_as_json_logic contains {...sd_show = false...}
• Advanced (conditional library): condition_as_complex_expression = Equals(intake.sd_show, False) with condition_as_json_logic = null

Step-by-Step Investigation Workflow

Step 1: Confirm the Symptom

Ask the support person for:

• Contract ID and link (https://app.spotdraft.com/contracts/v2/{contract_id})
• Workspace ID (WSID) and Cluster (US/IN/EU/ME)
• Specific fields showing wrong values (e.g., PEPM rate, billing cadence, employee count)
• When did the issue start? Was it after the questionnaire was edited?

Check contract data in Django Admin: