Mass action failure "Unsupported InstallAction for majorOS update" updating to Ventura

[Quokimo]

I know some of this has been covered once or twice before, but I'm VERY new to Jamf. I just recently started with this company and saw Jamf for the first time. Now, I'm basically the admin for an app I've only recently become acquainted with that manages computers running operating systems I've never supported in my short IT career. 
As you might imagine, I have a million questions, but I'll start with Mass Action commands.
After a bunch of attempts, I finally got 2 machines to update from 12.6.0 to 12.6.1, but when I try and get them to Ventura, I get this in Jamf: Unsupported InstallAction for majorOS update
It doesn't matter whether I've checked the option for majorOS update or not.
I always choose the option to defer as I was tasked to do.
When I run the mass action command, I see nothing on the target computers (no notifications etc) and after 5 minutes or so I get the failure result in Jamf. It's frustrating to say the least.
This happens on an iMac and a MacBook.
I have a third Mac that I test with and these commands worked the first time I tried. I went back and reset the OS to Catalina and mass action commands worked flawlessly a second time which gave me the false idea maybe this would be easy.
I've spent a good chunk of time over the past few weeks trying to figure this out for the other 2 machines. Anyone have any suggestions? I'm looking for a workable solution as my boss's boss wants a company-wide minimum OS policy that I can enforce at his discretion. At this point, I've got nothing to offer. 
I appreciate any assistance you all have to offer. 

[user-dIrrpGXxza · Accepted solution]

If I remember correctly, not all install actions are supported when you do a major update. I think it's either just download, or download, install and restart. I also seem to remember that allowing X number of deferrals is NOT supported when you do a major upgrade.

[oklair]

You are totally right and the Jamf documentation is quite clear about it:
https://learn.jamf.com/bundle/technical-paper-deploying-macos-upgrades-current/page/macOS_Updates_an...

However, as @bollman said, Jamf shouldn't allow us to send commands that are not supported. The GUI is literally misleading everyone, here. A more detailed message at the top or the page or a warning message after pressing "Apply" should be present.

I had lost so much time trying to understand what was going on...

[bollman]

Oh, come on.

We managed to hit this yesterday. Why is Jamf allowing us to send commands that are not supported?

[TheWarmAtlantic]

According to Apple we should be able to send this "upgrade" with delay command. I think this is a PI.

https://support.apple.com/guide/deployment/use-mdm-to-deploy-software-updates-depafd2fad80/web

[MatG]

@bollman Agree

the form should dynamically adjust as you select the options and only show what is available.
Really poor of jamf that its how it is.