Exception while emitting state count metrics for API records sync

Summary

The exception is caused by a 404 error indicating that the configuration for a standard workspace with a specific UUID could not be found. To fix this, the configuration for the workspace needs to be checked and corrected. It is not recommended to ignore this exception during data sync.


Question

Hi,
when syncing records from api through custom low code connector, I get this exception logged frequently all of a sudden.

io.airbyte.api.client.invoker.generated.ApiException: getWorkspace call failed with: 404 - {"message":"Internal Server Error: Could not find configuration for STANDARD_WORKSPACE: {workspace-uuid}.","exceptionClassName":"io.airbyte.commons.server.errors.IdNotFoundKnownException","exceptionStack":["io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find configuration for STANDARD_WORKSPACE: {workspace-uuid}.","\tat io.airbyte.server.apis.ApiHelper.execute(ApiHelper.java:32)","\tat io.airbyte.server.apis.WorkspaceApiController.getWorkspace(WorkspaceApiController.java:133)","\tat io.airbyte.server.apis.$WorkspaceApiController$Definition$Exec.dispatch(Unknown Source)","\tat io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invoke(AbstractExecutableMethodsDefinition.java:371)","\tat io.micronaut.context.DefaultBeanContext$4.invoke(DefaultBeanContext.java:594)","\tat io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:303)","\tat io.micronaut.web.router.RouteMatch.execute(RouteMatch.java:111)","\tat io.micronaut.http.context.ServerRequestContext.with(ServerRequestContext.java:103)","\tat io.micronaut.http.server.RouteExecutor.lambda$executeRoute$14(RouteExecutor.java:659)","\tat reactor.core.publisher.FluxDeferContextual.subscribe(FluxDeferContextual.java:49)","\tat reactor.core.publisher.InternalFluxOperator.subscribe(InternalFluxOperator.java:62)","\tat reactor.core.publisher.FluxSubscribeOn$SubscribeOnSubscriber.run(FluxSubscribeOn.java:194)","\tat io.micronaut.reactive.reactor.instrument.ReactorInstrumentation.lambda$init$0(ReactorInstrumentation.java:62)","\tat reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84)","\tat reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37)","\tat io.micronaut.scheduling.instrument.InvocationInstrumenterWrappedCallable.call(InvocationInstrumenterWrappedCallable.java:53)","\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)","\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)","\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)","\tat java.base/java.lang.Thread.run(Thread.java:1583)","Caused by: io.airbyte.config.persistence.ConfigNotFoundException: config type: STANDARD_WORKSPACE id: {workspace-uuid}","\tat io.airbyte.config.persistence.ConfigRepository.getStandardWorkspaceNoSecrets(ConfigRepository.java:263)","\tat io.airbyte.commons.server.handlers.WorkspacesHandler.getWorkspace(WorkspacesHandler.java:343)","\tat io.airbyte.server.apis.WorkspaceApiController.lambda$getWorkspace$4(WorkspaceApiController.java:133)","\tat io.airbyte.server.apis.ApiHelper.execute(ApiHelper.java:28)","\t... 19 more"],"rootCauseExceptionClassName":"java.lang.Class","rootCauseExceptionStack":["io.airbyte.config.persistence.ConfigNotFoundException: config type: STANDARD_WORKSPACE id: {workspace-uuid}","\tat io.airbyte.config.persistence.ConfigRepository.getStandardWorkspaceNoSecrets(ConfigRepository.java:263)","\tat io.airbyte.commons.server.handlers.WorkspacesHandler.getWorkspace(WorkspacesHandler.java:343)","\tat io.airbyte.server.apis.WorkspaceApiController.lambda$getWorkspace$4(WorkspaceApiController.java:133)","\tat io.airbyte.server.apis.ApiHelper.execute(ApiHelper.java:28)","\tat io.airbyte.server.apis.WorkspaceApiController.getWorkspace(WorkspaceApiController.java:133)","\tat io.airbyte.server.apis.$WorkspaceApiController$Definition$Exec.dispatch(Unknown Source)","\tat io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invoke(AbstractExecutableMethodsDefinition.java:371)","\tat io.micronaut.context.DefaultBeanContext$4.invoke(DefaultBeanContext.java:594)","\tat io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:303)","\tat io.micronaut.web.router.RouteMatch.execute(RouteMatch.java:111)","\tat io.micronaut.http.context.ServerRequestContext.with(ServerRequestContext.java:103)","\tat io.micronaut.http.server.RouteExecutor.lambda$executeRoute$14(RouteExecutor.java:659)","\tat reactor.core.publisher.FluxDeferContextual.subscribe(FluxDeferContextual.java:49)","\tat reactor.core.publisher.InternalFluxOperator.subscribe(InternalFluxOperator.java:62)","\tat reactor.core.publisher.FluxSubscribeOn$SubscribeOnSubscriber.run(FluxSubscribeOn.java:194)","\tat io.micronaut.reactive.reactor.instrument.ReactorInstrumentation.lambda$init$0(ReactorInstrumentation.java:62)","\tat reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84)","\tat reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37)","\tat io.micronaut.scheduling.instrument.InvocationInstrumenterWrappedCallable.call(InvocationInstrumenterWrappedCallable.java:53)","\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)","\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)","\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)","\tat java.base/java.lang.Thread.run(Thread.java:1583)"]}```
How to fix this exception? Is this a exception that can be ignored during data sync?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1709534744752909) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["exception", "state-count-metrics", "api-records-sync", "404-error", "standard-workspace", "workspace-uuid"]
</sub>

I am also getting the same error - would love to know if you find a solution.

I am getting the same error after upgrading to Destination V2 (Postgres).
The sync finished though. Should it be a concern?

we’re also receiving this error suddenly, we bumped airbyte version lately and are using a Redshift destination, but we haven’t upgraded to V2 yet

for what its worth its only affecting one custom connector, existing and new connectors are ok

if its any help i’ve noticed from checking the logs that it seems to be querying the getWorkspace endpoint with the connection uuid rather than the workspace uuid which is what causes this error

i dont have the logs to hand right now but if anyone wants an example i can fetch it