diff --git a/code/API_definitions/traffic-influence.yaml b/code/API_definitions/traffic-influence.yaml
index a62ade9..040e87d 100644
--- a/code/API_definitions/traffic-influence.yaml
+++ b/code/API_definitions/traffic-influence.yaml
@@ -606,6 +606,8 @@ paths:
           $ref: "#/components/responses/Generic403"
         "404":
           $ref: '#/components/responses/Generic404'
+        "409":
+          $ref: "#/components/responses/Generic409"
         "422":
           $ref: "#/components/responses/Generic422"
         "429":
diff --git a/code/Test_definitions/traffic-influence-postTrafficInfluence.feature b/code/Test_definitions/traffic-influence-postTrafficInfluence.feature
index f81df7a..2514c87 100644
--- a/code/Test_definitions/traffic-influence-postTrafficInfluence.feature
+++ b/code/Test_definitions/traffic-influence-postTrafficInfluence.feature
@@ -43,7 +43,7 @@ Feature: CAMARA Traffic Influence API, vwip - Operation postTrafficInfluence and
   @TI_Resource_LCM_Optional_Parameters_Valid_CREATE
   Scenario: Create Traffic Influence (TI) Resource with also optional parameters
     Given the request body property with mandatory valid parameters ("$.apiConsumerId", "$.appId")
-    And any other optional parameters (e.g. "$.AppInstanceId", "$.zone" etc.)
+    And any other optional parameters (e.g. "$.appInstanceId", "$.edgeCloudZoneId" etc.)
     And the request body is set to a valid request body
     When the HTTP "POST" request is sent
     Then it should be created a new TI Resource
diff --git a/code/Test_definitions/traffic-influence-postTrafficInfluenceDevice.feature b/code/Test_definitions/traffic-influence-postTrafficInfluenceDevice.feature
index 0de448a..97285ba 100644
--- a/code/Test_definitions/traffic-influence-postTrafficInfluenceDevice.feature
+++ b/code/Test_definitions/traffic-influence-postTrafficInfluenceDevice.feature
@@ -64,7 +64,7 @@ Feature: CAMARA Traffic Influence API, vwip - Operation postTrafficInfluenceDevi
   @TI_Resource_LCM_Optional_Parameters_Valid_CREATE_2-legs
   Scenario: Create Traffic Influence (TI) Resource with also optional parameters with 2 legs
     Given the request body property with mandatory valid parameters ("$.apiConsumerId", "$.appId", "$.device")
-    And any other optional parameters (e.g. "$.AppInstanceId", "$.zone" etc.)
+    And any other optional parameters (e.g. "$.appInstanceId", "$.edgeCloudZoneId" etc.)
     And the request body is set to a valid request body
     When the HTTP "POST" request is sent
     Then it should be created a new TI Resource
@@ -84,7 +84,7 @@ Feature: CAMARA Traffic Influence API, vwip - Operation postTrafficInfluenceDevi
   @TI_Resource_LCM_Optional_Parameters_Valid_CREATE_3-legs
   Scenario: Create Traffic Influence (TI) Resource with also optional parameters with 3 legs
     Given the request body property with mandatory valid parameters ("$.apiConsumerId", "$.appId")
-    And any other optional parameters (e.g. "$.AppInstanceId", "$.zone" etc.) with the request body set to a valid request body
+    And any other optional parameters (e.g. "$.appInstanceId", "$.edgeCloudZoneId" etc.) with the request body set to a valid request body
     And The header "Authorization" is set to a valid access token identifying a device
     When the HTTP "POST" request is sent
     Then it should be created a new TI Resource