cognigy flow execution stopped: missing slot value

Not specified by the original author.

TL;DR

Slots are the flow's memory: entities extracted from what the user said. 'Missing slot value' means a node asked for a slot that was never filled, so the flow has nothing to work with and stops. The fix is to guarantee the slot before the node that needs it: require it at an earlier step, or give the node a fallback for when it's empty. Flows should never assume a slot exists.

The query

cognigy flow execution stopped: missing slot value

Use this when

• Flow executions stop with a missing slot value error
• A flow works for some users but stops for others
• Slot-dependent branches never trigger

Not for

• Intents not matching user utterances
• Webhook failures inside flow nodes
• Cognigy API authentication errors

Steps

1. Find which slot is missing and where

Open the failed execution's trace and read which node stopped and which slot it wanted. Then check the slots filled earlier in the trace. The gap between 'slot needed' and 'slot filled' is the bug's location.

Expected output: the node, the slot name, and the point where filling should have happened.

2. Require the slot before it's needed

Add a slot-filling question upstream of the node that needs the value, with validation and reprompts. Don't let the flow reach a slot-dependent node with the slot possibly empty.

Expected output: the flow always arriving at the node with the slot filled.

3. Add a fallback for the empty case

Even with required slots, users dodge questions. Give the node a fallback: a default value, a graceful 'I need that to continue' reprompt, or a handoff. Belt and suspenders.

Expected output: a tested path for the user who never provides the value.

4. Check entity extraction for the slot

If the slot should have been filled from the user's message, the entity extraction is failing: the NLU didn't recognize the value. Add training examples for the phrasings users actually use.

Expected output: the slot filling correctly from real user phrasings.

Variant phrasings

cognigy slot not filled

Steps 1 and 4: trace the gap, then fix extraction.

cognigy flow stops unexpectedly

Step 2's upstream requirement prevents the whole class.

Why it happens

Flows are built happy-path first: the designer imagines the user answering every question, so every node assumes its inputs exist. Real users skip, dodge, and phrase things oddly. The missing slot is the flow discovering that its assumptions were optimistic, one stopped execution at a time.

Edge cases

• Slot lifetimes matter: a slot filled three turns ago may have expired. Check scope settings.
• Multi-language flows need slot validation per language. A regex that works in English fails elsewhere.
• Copied flows carry slot references that don't exist in the new flow. Audit after duplicating.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_wAFHZ5x-C6HOlMx5zVI1mA

Resolved from the public thread: https://vectle.com/posts/pst_wAFHZ5x-C6HOlMx5zVI1mA

Thread query: cognigy flow execution stopped: missing slot value

TL;DR: Slots are the flow's memory: entities extracted from what the user said. 'Missing slot value' means a node asked for a slot that was never filled, so the flow has nothing to work with and stops. The fix is to guarantee the slot before the node that needs it: require it at an earlier step, or give the node a fallback for when it's empty. Flows should never assume a slot exists.

Not specified by the original author.

TL;DR

"Parameter value missing in session" means the parameter was never set in session scope, was set in a narrower scope that expired, or was overwritten with an empty value. Trace the parameter's lifecycle: where it should be set (page, flow, or webhook), confirm the set actually ran, and read it back in session scope. Parameters do not teleport between scopes; every read needs a matching write in a scope that is still alive.

The query

dialogflow cx "parameter value missing in session"

Use this when

• Fulfillment reads parameters that are not there
• Parameters vanish between turns
• You are debugging parameter flow
• Form parameters do not reach webhooks

Not for

• Designing custom entities
• Writing training phrases
• Laying out pages and flows
• Intent matching issues

Steps

1. Identify where the parameter should be set

Map the expected lifecycle: form parameter on a page, flow-scoped value, or webhook-set session parameter. If no step in the flow actually sets it, the bug is a missing write, not a missing read.

Expected output: the intended set-point identified.

2. Confirm the set step actually executed

Check the conversation path: did the flow reach the page with the form, did the webhook run and return the parameter? Skipped steps (conditional routes, early exits) are the most common reason a set never happens.

Expected output: set-step execution confirmed or the skip found.

3. Check the scope the parameter was set in

Page-scoped parameters die when the page exits; flow-scoped die when the flow exits. If the read happens in a later page or flow, the parameter must be set in session scope. Scope mismatch is the classic cause.

Expected output: scope of the write matching the scope of the read.

4. Guard against overwrites with empty values

A later step setting the same parameter to empty wipes it silently. Search the flow for every write to that parameter name and ensure none fire unintentionally. One stray preset can empty a parameter mid-conversation.

Expected output: no unintended writes to the parameter.

5. Log parameter state at webhook entry

Have webhooks log the session parameters they receive. The log shows exactly what the platform delivered versus what the flow designer assumed. Assumptions about parameters are where these bugs hide.

Expected output: webhook-entry parameter logging in place.

Template: the checklist

Session parameter debugging:
[ ] Intended set-point mapped for the parameter
[ ] Set-step execution confirmed in the path
[ ] Write scope matching read scope (session where needed)
[ ] No stray overwrites emptying the parameter
[ ] Webhook-entry parameter logging enabled

Variant phrasings

dialogflow cx session parameter empty

Steps 1 and 3. Find the set-point, fix the scope.

parameter not passed to webhook

Steps 2 and 5. Confirm the set ran, log what arrived.

form parameter missing in fulfillment

Steps 3 and 4. Scope plus overwrite check.

Why it happens

Dialogflow CX scopes parameters to pages, flows, and sessions, and each scope has a lifetime tied to the conversation's position in the flow graph. Designers think in terms of "the order id" as a global fact; the platform thinks in terms of scoped storage with expiry. The mismatch between the mental model (global) and the actual model (scoped) produces exactly this error.

Edge cases

• Parameter presets on routes: route-level presets can overwrite session values unexpectedly. Audit route presets.
• Session TTL expiry: very long conversations can outlive parameter retention. Refresh critical parameters.
• Multi-flow architectures: parameters set in one flow are invisible in another unless session-scoped. Design cross-flow parameters explicitly.
• Webhook response parameter naming: a typo in the response parameter name sets a new parameter instead of the intended one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_2il6VVq64ap7mv4KpGV3Ig

Resolved from the public thread: https://vectle.com/posts/pst_2il6VVq64ap7mv4KpGV3Ig

Thread query: dialogflow cx "parameter value missing in session"

TL;DR: "Parameter value missing in session" means the parameter was never set in session scope, was set in a narrower scope that expired, or was overwritten with an empty value. Trace the parameter's lifecycle: where it should be set (page, flow, or webhook), confirm the set actually ran, and read it back in session scope. Parameters do not teleport between scopes; every read needs a matching write in a scope that is still alive.

Not specified by the original author.

TL;DR

Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts

Use this when

• You see this exact message or symptom in Gainsight: Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Gainsight fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the rule action field mapping, the scorecard measure config, the source object fields, and the 360 page sections, and check the last successful refresh timestamp, the forced refresh result, and the served value versus the direct source query. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Verify: the corrected value or setting is visible in Gainsight itself, not only in a local config file
4. Re-run the original operation on the single affected item first: re-run the rule or scorecard job for one company, then open that company in C360 and check the created task or measure. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the success plan objective task assigned to the owner and the scorecard measure showing a value instead of a blank. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Gainsight version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Gainsight NXT Rules Engine and Scorecards 2.0, Salesforce or Snowflake data sources, C360 layouts. The steps assume you can read the job or build log and change the named object in Gainsight.

Why it happens

In Gainsight, this failure usually means an upstream refresh stopped or a cached or default value is being served in place of a freshly calculated one, so the surface looks plausible while being old. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_TPDIthXsW3IP7BLliTqhzw

Resolved from the public thread: https://vectle.com/posts/pst_TPDIthXsW3IP7BLliTqhzw

Thread query: Gainsight Scorecard measure value is null for usage percentile: health scores blank for mid-market accounts

TL;DR: Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Start in the Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.