Removing optional input field causing error message on custom connector

Summary

Error message occurs after removing optional input field from custom connector in prod environment


Question

We have created a custom connector and due to the high volume of incoming data, we added an optional input field (Adgroup) to filter the data. Now we want to remove this filter to run the connection in a prod environment and this is the error message that shows up after we removed the input value and clicked on Test and Save



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["custom-connector", "optional-input-field", "error-message", "prod-environment"]
Failure origin: source```
2024-01-22 09:31:52 platform > Creating stdout socket server...
2024-01-22 09:31:52 platform > Creating stderr socket server...
2024-01-22 09:31:52 platform > Creating pod ive-manifest-check-ace17b66-a865-4fa3-ac39-0d22c4e45458-0-uyenb...
2024-01-22 09:31:52 platform > Waiting for init container to be ready before copying files...
2024-01-22 09:31:53 platform > Init container ready..
2024-01-22 09:31:53 platform > Copying files...
2024-01-22 09:31:53 platform > Uploading file: source_config.json
2024-01-22 09:31:53 platform > kubectl cp /tmp/9673635b-4c5b-429e-a150-8f053284a132/source_config.json jobs/ive-manifest-check-ace17b66-a865-4fa3-ac39-0d22c4e45458-0-uyenb:/config/source_config.json -c init
2024-01-22 09:31:53 platform > Waiting for kubectl cp to complete
2024-01-22 09:31:54 platform > kubectl cp complete, closing process
2024-01-22 09:31:54 platform > Uploading file: FINISHED_UPLOADING
2024-01-22 09:31:54 platform > kubectl cp /tmp/8a0069e7-917d-4083-9672-47199cc8b3a0/FINISHED_UPLOADING jobs/ive-manifest-check-ace17b66-a865-4fa3-ac39-0d22c4e45458-0-uyenb:/config/FINISHED_UPLOADING -c init
2024-01-22 09:31:54 platform > Waiting for kubectl cp to complete
2024-01-22 09:31:54 platform > kubectl cp complete, closing process
2024-01-22 09:31:54 platform > Waiting until pod is ready...
2024-01-22 09:31:55 platform > Setting stdout...
2024-01-22 09:31:55 platform > Setting stderr...
2024-01-22 09:31:56 platform > Reading pod IP...
2024-01-22 09:31:56 platform > Pod IP: 10.17.54.146
2024-01-22 09:31:56 platform > Using null stdin output stream...
2024-01-22 09:31:56 platform > Reading messages from protocol version 0.2.0```

<@U05DJ8GSFCJ> is this in Airbyte Cloud or self-hosted?

Airbyte Cloud <@U02TQLBLDU4>
it’s the same use case as https://airbytehq.slack.com/archives/C01AHCD885S/p1705592267834409