<@U04S8PLJWMT> When i fork the Hubspot connector, ...
# replication-ask-ai
p
@kapa.ai When i fork the Hubspot connector, it throws an error straight away in the editor
k
Based on the knowledge sources available, there is a mention of an error encountered when forking/editing the HubSpot connector in the Connector Builder. One user reported that when directly navigating to the editor URL (rather than going through the normal UI flow), they encountered this error:
Copy code
{
  "message": "Internal Server Error: not yet implemented",
  "exceptionClassName": "java.lang.UnsupportedOperationException",
  "exceptionStack": [],
  "rootCauseExceptionStack": []
}
The workaround identified for this issue was to navigate through the UI normally rather than going directly to the URL: [403 error on custom connector] 1. Open Airbyte 2. Go to Builder 3. Open the connection you want to edit from there Directly pasting/opening the Builder URL in a new tab caused the error, even before authentication. However, the knowledge sources don't provide detailed information about other types of errors you might encounter when forking the HubSpot connector. Could you share the specific error message you're seeing? That would help narrow down the cause. Additionally, there is a known issue where forking a CDK-based connector like HubSpot can result in errors in the Connector Builder, as mentioned briefly in the context of user-defined cursor feature requests. [user-defined cursor discussion] If the error you're seeing is different from the above, the knowledge sources do not contain enough information to provide a more specific answer. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.