@kapa.ai: 2026-04-09 234548,645 [io-executor-thread-1] ERROR i.a.c.s.e.h.UncaughtExceptionHandler(handle):33 - Uncaught exception io.temporal.client.WorkflowNotFoundException: workflowId='spec_0f554629-6cad-47f7-8f27-3e64e3390286', runId='', workflowType='ConnectorCommandWorkflow'

The error you're seeing:

io.temporal.client.WorkflowNotFoundException: workflowId='spec_0f554629-6cad-47f7-8f27-3e64e3390286', runId='', workflowType='ConnectorCommandWorkflow'

indicates that Airbyte's worker is trying to interact with a Temporal workflow (specifically a

ConnectorCommandWorkflow

for a spec operation) that no longer exists or has already completed/been cleaned up. This is a known class of issues in Airbyte where Temporal workflow state becomes inconsistent. Based on the knowledge sources, similar errors have been observed in several scenarios: • Workflow already completed: The worker attempts to report results back to a Temporal workflow that has already finished. This manifests as

NOT_FOUND: workflow execution already completed

errors in related cases. [Forum Post] • Stuck workflows: Temporal workflows can get stuck, causing the

CONNECTION_UPDATER

or other task queues to stop processing, which may result in workflows being terminated or lost. [GitHub Issue] • Workflow task processing failures:

InternalWorkflowTaskException

errors during replay can cause workflows to become stuck or be dropped. [GitHub Issue] Suggested steps to investigate: 1. Check worker logs for additional context around the same timestamp — look for

InternalWorkflowTaskException

,

NOT_FOUND

, or resource exhaustion errors. 2. Check resource availability — insufficient memory or CPU on the node can cause pods/workflows to be killed unexpectedly. 3. Restart Airbyte services — particularly the

worker

and

temporal

components, as stuck workflows sometimes resolve after a restart. 4. Check Temporal service health — ensure the Temporal service itself is healthy and not experiencing connectivity issues. The knowledge sources do not contain a definitive root cause or fix specifically for

WorkflowNotFoundException

on

ConnectorCommandWorkflow

, so if the issue persists, I'd recommend opening a GitHub issue with your full logs for further investigation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.