@rtolsma
I'm sorry to hear that you're experiencing issues with the OpenAPI specification and the client SDK generation. It sounds like there might be some discrepancies or errors in the OpenAPI document that need to be addressed.
For the issue with the duplicate enum, it's great that you were able to identify and fix it. However, if you're encountering further problems with the schemas not being processed correctly, this could be due to a variety of reasons such as missing types, incorrect references, or other structural issues within the OpenAPI document.
To resolve this, I would recommend the following steps:
1. **Validate the OpenAPI Specification**: Use an OpenAPI validator tool to check for any structural issues or errors in the specification document.
2. **Review the Specification**: Manually review the specification to ensure that all schemas are defined correctly, with proper type definitions and references.
3. **Contact Support**: If the issues persist after validation and review, it would be best to reach out to the support team with specific details about the errors you're encountering. They may need to update the OpenAPI specification to fix these issues.
4. **Generate SDK with Corrections**: Once the OpenAPI specification is validated and any necessary corrections are made, try generating the client SDK again.
If you need further assistance or would like to report the issues to the support team, please let me know, and I can help facilitate that process.