vaInputs.variable does not store value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2020 06:33 AM
I have been working on chatbot and retrieving values on basis of vaInputs.variable name but sometimes it doesnt hold value any specific reason to that ?, my version is NewYork
Workaround for same : have to use Script and use vaVars.Variable_name = vaInputs.Variable and then use that vavrs.variable for retrieving same value but this makes workflow very long and heavy
- Labels:
-
Virtual Agent
- 1,743 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2020 06:42 AM
Hi there,
Not sure what you mean here. Can you share an example?
If my answer helped you in any way, please then mark it as helpful.
Kind regards,
Mark
2020 ServiceNow Community MVP
2020 ServiceNow Developer MVP
---
LinkedIn
Community article list
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2021 05:13 AM
I have same issue, with all types of variables.
I've cretaed rather complex conversation with few conditional blocks. And 2 last questions are not stored after pass conditional block, value is cleared. As workaround i need to copy value vaVars.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2020 07:30 AM
This I think is the same exact issue I just posted about myself after getting frustrated that one more time...
Occasional issue - Reference Input value becomes NULL later in flow
I've run into this a few times and have the same workaround as you. No clear indicator as to why it happens, but if I recall, it seems like it's only Reference Inputs, but not all of them (as clear in my example). And they don't lose their value immediately - hence the workaround of creating a script to save it as a variable right after - but they do lose their value after a couple step
We're on Madrid but I'm not even gonna waste my time recreating it in my Personal Orlando instance because it's so sporadic I probably couldn't recreate it if I tried.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2020 05:13 PM
hey Chris, but this is happening with me even in Input boxes also along with reference ones, i ended up adding almost same numbers of script to hold those variable values and store using vaVars.variable name , but i did not find this in orlando, may be they resolved this but nothing officially surfaced out. 🙂