I’m not sure how it is done in 3.2 (unfortunately I don’t have access to 3.2 at the moment), but in 3.1 there is a table “custom_section_orders” in the database. If you take a look of all the sections which are associated with your issue, you will probably notice that the problematic section isn’t listed. If you add this section in the table, you’ll be able to order it. It’s an issue we have many times. I think it happens if a section was createad after starting the issue. In the old OJS Version (2.X) there was a button to set the sections to the default status which helped, but this workaround is missing in 3.X.
Kind regards
Daniela