This message was deleted.
# replication-ask-ai
s
This message was deleted.
k
The error in your logs indicates an invalid JWT signature when Airbyte tries to authenticate with Google Cloud Storage using the service account
airbyte-sa@plus500-gke-qa.iam.gserviceaccount.com
. Specifically:
Copy code
{
  "error": "invalid_grant",
  "error_description": "Invalid JWT Signature."
}
This means the service account credentials (the private key used to sign the JWT) are invalid, expired, or corrupted. This is the same class of authentication problem seen with other Google connectors in Airbyte. [source-google-analytics issue] Most likely causes: 1. The service account JSON key has been revoked or rotated — the private key stored in Airbyte no longer matches the active key in GCP. 2. The private key in the credentials is malformed — e.g., newlines (
\n
) in the private key were not properly preserved when the JSON was entered into Airbyte's configuration. 3. The service account has been deleted or disabled in GCP. Recommended steps to resolve: 1. Go to the Google Cloud Console → IAM & Admin → Service Accounts and verify that
airbyte-sa@plus500-gke-qa.iam.gserviceaccount.com
is active. 2. Generate a new JSON key for the service account. 3. Update the credentials in your Airbyte configuration with the new key, ensuring the private key field is correctly formatted (with proper
\n
line breaks). 4. Re-test the connection. The knowledge sources do not contain specific documentation for this exact error in the GCS storage client context, but the root cause (invalid service account credentials) and the remediation steps above are consistent with similar authentication failures documented for other Google connectors in Airbyte. [source-google-analytics issue] šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
a
@kapa.ai now i see this in server logs 2026-04-16 120322,576 [io-executor-thread-7] ERROR i.a.s.a.ApiHelper(execute):47 - Unexpected Exception io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find attempt stats for job_id: 125800 and attempt no: 0 at io.airbyte.commons.server.handlers.AttemptHandler.getAttemptCombinedStats(AttemptHandler.kt:251) at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats$lambda$2(AttemptApiController.kt:66) at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32) at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats(AttemptApiController.kt:65) at io.airbyte.server.apis.controllers.$AttemptApiController$Definition$Exec.dispatch(Unknown Source) at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461) at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4438) at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272) at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38) at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:465) at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:442) at io.micronaut.core.execution.ExecutionFlow.lambda$async$0(ExecutionFlow.java:92) at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:232) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) 2026-04-16 120322,596 [io-executor-thread-7] ERROR i.a.c.s.e.h.IdNotFoundExceptionHandler(handle):33 - Not found exception class NotFoundKnownExceptionInfo { id: null message: Id not found: Could not find attempt stats for job_id: 125800 and attempt no: 0 exceptionClassName: io.airbyte.commons.server.errors.IdNotFoundKnownException exceptionStack: [io.airbyte.commons.server.errors.IdNotFoundKnownException: Id not found: Could not find attempt stats for job_id: 125800 and attempt no: 0, at io.airbyte.commons.server.errors.handlers.IdNotFoundExceptionHandler.handle(IdNotFoundExceptionHandler.kt:32), at io.airbyte.commons.server.errors.handlers.IdNotFoundExceptionHandler.handle(IdNotFoundExceptionHandler.kt:24), at io.micronaut.http.server.RequestLifecycle.lambda$handlerExceptionHandler$10(RequestLifecycle.java:314), at io.micronaut.http.server.RequestLifecycle.handlerExceptionHandler(RequestLifecycle.java:326), at io.micronaut.http.server.RequestLifecycle.onErrorNoFilter(RequestLifecycle.java:253), at io.micronaut.http.server.RequestLifecycle.lambda$onErrorNoFilter$2(RequestLifecycle.java:215), at io.micronaut.core.execution.ImperativeExecutionFlowImpl.onErrorResume(ImperativeExecutionFlowImpl.java:112), at io.micronaut.core.execution.DelayedExecutionFlowImpl$OnErrorResume.apply(DelayedExecutionFlowImpl.java:393), at io.micronaut.core.execution.DelayedExecutionFlowImpl.work(DelayedExecutionFlowImpl.java:58), at io.micronaut.core.execution.DelayedExecutionFlowImpl.completeLazy(DelayedExecutionFlowImpl.java:80), at io.micronaut.core.execution.DelayedExecutionFlowImpl.completeExceptionally(DelayedExecutionFlowImpl.java:104), at io.micronaut.core.execution.DelayedExecutionFlow.complete(DelayedExecutionFlow.java:100), at io.micronaut.core.execution.ImperativeExecutionFlowImpl.onComplete(ImperativeExecutionFlowImpl.java:132), at io.micronaut.core.execution.ExecutionFlow.lambda$async$0(ExecutionFlow.java:92), at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:232), at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144), at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642), at java.base/java.lang.Thread.run(Thread.java:1583), Caused by: io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find attempt stats for job_id: 125800 and attempt no: 0, at io.airbyte.commons.server.handlers.AttemptHandler.getAttemptCombinedStats(AttemptHandler.kt:251), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats$lambda$2(AttemptApiController.kt:66), at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats(AttemptApiController.kt:65), at io.airbyte.server.apis.controllers.$AttemptApiController$Definition$Exec.dispatch(Unknown Source), at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461), at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4438), at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272), at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38), at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:465), at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:442), ... 5 more] rootCauseExceptionClassName: java.lang.Class rootCauseExceptionStack: [io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find attempt stats for job_id: 125800 and attempt no: 0, at io.airbyte.commons.server.handlers.AttemptHandler.getAttemptCombinedStats(AttemptHandler.kt:251), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats$lambda$2(AttemptApiController.kt:66), at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats(AttemptApiController.kt:65), at io.airbyte.server.apis.controllers.$AttemptApiController$Definition$Exec.dispatch(Unknown Source), at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461), at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4438), at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272), at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38), at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:465), at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:442), at io.micronaut.core.execution.ExecutionFlow.lambda$async$0(ExecutionFlow.java:92), at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:232), at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144), at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642), at java.base/java.lang.Thread.run(Thread.java:1583)] } and the airbyte-workload-launcher keep crashing with: 2026-04-16 120352,181 [main] INFO i.m.c.e.DefaultEnvironment(<init>):170 - Established active environments: [k8s, control-plane, edition-community] 2026-04-16 120358,084 [main] INFO c.z.h.HikariDataSource(<init>):79 - config-pool - Starting... 2026-04-16 120358,274 [main] INFO c.z.h.HikariDataSource(<init>):81 - config-pool - Start completed. 2026-04-16 120359,068 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.netty' 2026-04-16 120359,069 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'ERROR' for logger: 'com.zaxxer.hikari' 2026-04-16 120359,069 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.grpc' 2026-04-16 120359,069 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'ERROR' for logger: 'com.zaxxer.hikari.pool' 2026-04-16 120359,070 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.fabric8.kubernetes.client' 2026-04-16 120407,386 [scheduled-executor-thread-2] INFO i.a.w.l.PodSweeper(sweepPods):56 - Starting pod sweeper cycle in namespace [airbyte]... 2026-04-16 120407,392 [scheduled-executor-thread-2] INFO i.a.w.l.PodSweeper(sweepPods):88 - Will sweep Succeeded pods older than 2026-04-16T115407.387Z (UTC). 2026-04-16 120407,460 [scheduled-executor-thread-2] INFO i.a.w.l.PodSweeper(sweepPods):91 - Will sweep unsuccessful pods older than 2026-04-16T100407.387Z (UTC). 2026-04-16 120415,474 [scheduled-executor-thread-1] INFO i.a.f.ConfigFileClient(<init>):141 - path /flags does not exist, will return default flag values 2026-04-16 120418,277 [scheduled-executor-thread-1] INFO i.a.w.l.p.c.WorkloadApiQueueConsumer(initialize):41 - Initializing ApiQueueConsumer for e9104a14-4a4a-4c51-bb69-c86d9188034f 2026-04-16 120418,376 [scheduled-executor-thread-1] INFO i.a.w.l.p.c.WorkloadApiQueuePoller(initialize):53 - Initalizing ApiQueuePoller with e9104a14-4a4a-4c51-bb69-c86d9188034f and default 2026-04-16 120418,580 [scheduled-executor-thread-1] INFO i.a.w.l.p.c.WorkloadApiQueuePoller(initialize):53 - Initalizing ApiQueuePoller with e9104a14-4a4a-4c51-bb69-c86d9188034f and high 2026-04-16 120418,694 [main] INFO i.a.w.l.a.DataplaneIdentityService(initialize):55 - Running as f9d357d5-ecfe-4bab-a16a-94d09e3002f8 (b638320f-318c-4995-ac62-7623a94acc8e) for 2026-04-16 120418,793 [main] INFO i.m.r.Micronaut(start):101 - Startup completed in 39583ms. Server Running: http://airbyte-workload-launcher-6875f76474-j5hrg:8016 2026-04-16 120418,883 [Thread-2] INFO i.a.w.l.ClaimedProcessor(getWorkloadList):91 - requesting workload list: WorkloadListRequest(dataplane=[f9d357d5-ecfe-4bab-a16a-94d09e3002f8], status=[claimed], updatedBefore=null) 2026-04-16 120422,387 [Thread-2] INFO i.a.w.l.ClaimedProcessor(retrieveAndProcess):58 - Re-hydrating 1 workload claim(s)... 2026-04-16 120422,389 [Thread-3] INFO i.a.w.l.p.c.WorkloadApiQueuePoller(resumePolling):68 - Resuming ApiQueuePoller with e9104a14-4a4a-4c51-bb69-c86d9188034f and high 2026-04-16 120422,389 [Thread-3] INFO i.a.w.l.p.c.WorkloadApiQueuePoller(resumePolling):68 - Resuming ApiQueuePoller with e9104a14-4a4a-4c51-bb69-c86d9188034f and default 2026-04-16 120422,784 [process-claimed-scheduler-2] INFO i.a.w.l.p.s.m.Stage(apply):42 - APPLY Stage: BUILD — (workloadId=80b8c669-def7-4638-a601-587942af8754_125800_0_check) 2026-04-16 120425,273 [scheduled-executor-thread-2] INFO i.a.w.l.PodSweeper(sweepPods):149 - Completed pod sweeper cycle. 2026-04-16 120425,876 [Thread-4] INFO i.m.r.Micronaut(lambda$start$0):120 - Embedded Application shutting down
k
You are seeing two related issues that are likely connected to the GCS authentication failure you saw earlier. 1. "Missing stats for job" / IdNotFoundKnownException The error
Could not find attempt stats for job_id: 125800 and attempt no: 0
means Airbyte's server is trying to retrieve sync statistics for a job attempt, but those stats were never written. This is a known symptom when the workload output cannot be persisted to storage — in your case, because the GCS credentials are invalid (as seen in your previous error). Since the sync results/stats couldn't be written to GCS, the server finds nothing when it tries to look them up. [Forum: Missing stats warning] 2. airbyte-workload-launcher crashing Looking at the launcher logs, it starts up successfully, initializes, and then shuts down after ~7 seconds:
Copy code
2026-04-16 12:04:18,793 - Startup completed in 39583ms.
...
2026-04-16 12:04:25,876 - Embedded Application shutting down
This crash-loop pattern in the workload-launcher is consistent with a storage connectivity failure. When the launcher cannot successfully connect to or write to the configured storage backend (GCS in your case), it can enter a zombie/crash state. [workload-launcher liveness probe issue] Root Cause Both issues trace back to the invalid GCS service account credentials (
Invalid JWT Signature
) you identified in the previous error. The workload-launcher and server both depend on GCS for writing workload outputs and logs. With broken credentials: • Workload outputs/stats cannot be written → "missing stats" errors • The workload-launcher fails to operate and crashes What to do 1. Fix the GCS credentials first — rotate the service account key and update it in your Airbyte configuration (as described in the previous answer). 2. Once credentials are valid, restart the
airbyte-workload-launcher
pod
to clear the crash loop. 3. Any jobs stuck in a hung/launched state may need to be manually cancelled and re-triggered after the fix. [workload-launcher liveness probe issue] šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.