It looks like you're encountering an issue where your new stream doesn't have a schema, leading to the error "No properties node in stream schema." This is a common issue when the JSON schema for the stream is not properly defined. From the knowledge sources, it appears that the error you're seeing is similar to the one discussed in the forum and GitHub issues. The error typically occurs during the normalization step when the

properties

field of the JSON schema is missing or not properly defined. Here are some steps you can take to resolve this issue: 1. Define the JSON Schema: Ensure that your stream's JSON schema includes the

properties

field. Even if your old streams are working without a schema, it's a good practice to define it explicitly to avoid such errors. 2. Check the Schema Structure: Make sure your schema is structured correctly. Here is an example of a properly defined JSON schema:

json     {       "streams": [         {           "name": "your_stream_name",           "json_schema": {             "type": "object",             "properties": {               "field1": {                 "type": "string"               },               "field2": {                 "type": "integer"               }               // Add more fields as necessary             }           }         }       ]     }

3. Review Existing Documentation: If you're using Airbyte's low-code CDK, refer to the [low-code CDK overview](https://docs.airbyte.com/connector-development/config-based/low-code-cdk-overview/) for guidance on how to properly define your connector's schema. 4. Example from Knowledge Sources: Here is an example from the knowledge sources that shows a JSON schema structure:

json     {       "streams": [         {           "destination_sync_mode": "append",           "sync_mode": "incremental",           "stream": {             "name": "incremental_transaction_stream",             "json_schema": {               "type": "object",               "required": [                 "transactionId",                 "paymentProvider",                 "customerId"               ],               "properties": {                 "transactionId": {                   "type": "string"                 },                 "paymentProvider": {                   "type": "string"                 },                 "customerId": {                   "type": "string"                 }               }             }           }         }       ]     }

By ensuring that your stream's JSON schema includes the

properties

field and is correctly structured, you should be able to resolve the "No properties node in stream schema" error. For more detailed guidance, you can refer to the [low-code CDK documentation](https://docs.airbyte.com/connector-development/config-based/low-code-cdk-overview/). If you continue to face issues, please provide more details about your schema and the specific error logs, and I can assist you further.