I'm running into an issue with the Resize Volume command. At a high level, it has 3 mandatory parameters and it's complaining that it's only receiving 2 - the one missing is the TargetSize. I'm at a loss at this point for why this variable isn't getting passed since I am inputting it and the user inputs report the value. I do have this user input classified as a number. I suspect I'm missing something rather obvious but I just don't see it yet.
Here are some screenshots with the Find Chart first:
And now the user inputs tab from the Planning Failed window:
Looking at the code for the command I know that size_mb tracks back to TargetSize which is the parameter WFA is complaining about not being there. Yet as you can see from the second screenshot I am inputting a number that I see as acceptable. Any insight is much appreciated, thanks!
Yes, I am trying to first confirm the named volume to resize actually exists. Then I confirm that the aggregate that contains this volume has enough space to accommodate the size increase requested while still remaining under a maximum utilization percentage.
I will take a look at the example you uploaded, thanks!
Ah I see now, I remove the first column (or made it unviewable and ignored it). I guess I don't understand why the Resize Volume command has 2 columns, one for new volume and one for volume. In my mind, I'm simply resizing an existing volume so why do I need 2 columns of activity? I'll update the first column with the same FindChart and see if that works.
Okay, this is driving me mad (well, not really). I'll create a find chart under the New Volume column, save it and then when I go back to edit it it's gone! But wait, it's not actually gone it now exists under the Volume column ?!?!?! I don't understand this at all, why would the find chart move to a different column when i specifically edited the first column?
Yet in your example both columns are using the same find chart. I think this may be why I removed the original column...
This does help - I think I was initially getting confused around why the TargetSize parameter is mapped to a different object name (and all the others). This does make sense and allows for breaking down the flow into smaller chunks if desired. I am however getting confused as to why my variable doesn't seem to remain attached to the find chart I create for it. The find chart still exists but the NewVolume variable doesn't pull it up after I create it (clicking on the variable brings up a new FindChart template right after I saved the one I created).
Shoot, never mind, I just realized why - I was using different variable names in the variable field vs. the field in the spreadsheet. Okay, now I think I'm good. Whew!
Oh yeah, I really like the auto-complete feature and make heavy use of it.
I did finally get this flow working and as expected, the troubles I was having were due to mistakes on my part. Incidentally, our UI takes the resize request in the form of usable MB but the Resize Volume command doesn't inherently adjust for a given snap reserve. In case it's useful to anyone else, here's the formula I'm using to account for that in the Define node for size_mb: