Giacomo Chiarella
07/23/2025, 6:16 AM{"status":500,"type":"<https://reference.airbyte.com/reference/errors>
","title":"unexpected-problem","detail":"An unexpected problem has occurred. If this is an error that needs to be addressed, please submit a pull request or github issue.","documentationUrl":null,"data":{"message":"bound must be greater than origin"}}
when I called the method PATCH on the endpoint /api/public/v1/destinations/{d[‘destinationId’]} to change the password. What is it about?kapa.ai
07/23/2025, 6:16 AM{
"status": 500,
"type": "<https://reference.airbyte.com/reference/errors>",
"title": "unexpected-problem",
"detail": "An unexpected problem has occurred. If this is an error that needs to be addressed, please submit a pull request or github issue.",
"documentationUrl": null,
"data": {
"message": "bound must be greater than origin"
}
}
indicates an internal server error (HTTP 500) when calling the PATCH method on /api/public/v1/destinations/{destinationId}
to change the password. Based on the knowledge sources, this type of error is a generic server-side error in Airbyte, often labeled as "unexpected-problem." The specific message "bound must be greater than origin"
suggests there may be an issue with the values provided in your request payload—possibly a configuration parameter that expects a certain numeric relationship (e.g., a range or limit) where the upper bound must be greater than the lower bound. While there are several reports of 500 errors when updating or patching destinations (or other resources) in Airbyte, the root causes vary, including misconfigurations, missing secrets, or internal validation issues. For example, similar errors have occurred due to missing secrets in the destination configuration or invalid configuration values, but none of the sources mention this exact error message or a direct fix for it. The OpenAPI spec confirms that PATCH is a supported method for updating destinations, but does not specify this error scenario or its resolution [Airbyte Public API - Destinations](https://raw.githubusercontent.com/airbytehq/airbyte-platform/f284238f0099c4c0a3542d4c42a88773c45c363d/airbyte-api/src/main/openapi/api.yaml). What you can do: - Double-check your PATCH request payload, especially any fields that might represent a range or have minimum/maximum values, to ensure all values are valid and logical. - If the error persists and you cannot identify a misconfiguration, it may be an internal bug or an unhandled edge case. In that case, following the error message's suggestion to submit a GitHub issue with your request details would be appropriate. I'm sorry, but the knowledge sources do not contain a more specific explanation or solution for the "bound must be greater than origin"
error in this context.Giacomo Chiarella
07/23/2025, 6:19 AM{"status":500,"type":"<https://reference.airbyte.com/reference/errors>
","title":"unexpected-problem","detail":"An unexpected problem has occurred. If this is an error that needs to be addressed, please submit a pull request or github issue.","documentationUrl":null,"data":{"message":"bound must be greater than origin"}}
when I called the method PATCH on the endpoint /api/public/v1/destinations/{d[‘destinationId’]} to change the password. What is it about?
The request just has this payload
{
"configuration": {
"password": db_password,
"destinationType": "postgres"
}
}
there are no parameters which can be “greater than”kapa.ai
07/23/2025, 6:19 AMkapa.ai
07/23/2025, 6:19 AM"bound must be greater than origin"
when using the PATCH method on /api/public/v1/destinations/{destinationId}
to update the password. The available documentation and issues reference generic 500 errors and internal server errors when updating destinations, but do not mention this particular error message or its root cause. Your payload appears correct for updating a password, and there are no obvious "bound" or "origin" parameters in your example. This suggests the error may be due to an internal validation or a bug in Airbyte's backend, possibly related to how it processes the configuration object or its schema validation. If you continue to encounter this error, the best course of action is to submit a detailed issue on GitHub, as suggested in the error message, including your payload and the context of your request. This will help the Airbyte team investigate further. Again, the knowledge sources do not provide a direct answer or workaround for this specific error.