This is a known issue affecting vRealize Automation 7.5 and below, currently there is no resolution.
Workaround:
To workaround this issue:
Add a placeholder or dummy property as a
COMPUTED variable named "
00000" to be consumed first.
Note: Only the first property exemplifies this issue in the output.properties file.