I am doing sync from Mixpanel. I created Mixpanel source which was successful. I created target as Postgres DB and it is successful. But when I create a connection, it is giving error on Streams "No catalog found in source discovery output" Pod Logs: [ec2-user@ip-10-201-11-120 ~]$ KUBECONFIG=/home/ec2-user/.airbyte/abctl/abctl.kubeconfig kubectl logs -n airbyte-abctl mixpanel-discover-4595e8de-efd1-41f5-af3e-54c84c8e4e4a-0-pcprl -c connector-sidecar Unsetting empty environment variable 'DATA_PLANE_SERVICE_ACCOUNT_CREDENTIALS_PATH' Unsetting empty environment variable 'DATA_PLANE_SERVICE_ACCOUNT_EMAIL' Unsetting empty environment variable 'AWS_SECRET_ACCESS_KEY' Unsetting empty environment variable 'AWS_ACCESS_KEY_ID' Unsetting empty environment variable 'S3_PATH_STYLE_ACCESS' 2026-06-12 163138,744 [main] INFO i.a.c.ApplicationKt(main):14 - Sidecar start _ _ _ _ / | (_)____/ /_ __ __/ /____ / /| | / / ___/ __ \/ / / / __/ _ \ / _ |/ / / / /_/ / /_/ / /_/ __/ /_/ |_/_/_/ /_.___/\__, /\__/\___/ /____/ : airbyte-connector-sidecar : 2026-06-12 163139,934 [main] INFO i.m.c.e.DefaultEnvironment(init):170 - Established active environments: [worker-v2, k8s, control-plane, edition-community] 2026-06-12 163140,673 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.netty' 2026-06-12 163140,674 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'ERROR' for logger: 'com.zaxxer.hikari' 2026-06-12 163140,674 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.grpc' 2026-06-12 163140,674 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.temporal' 2026-06-12 163140,674 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'ERROR' for logger: 'com.zaxxer.hikari.pool' 2026-06-12 163140,674 [main] INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):113 - Setting log level 'INFO' for logger: 'io.fabric8.kubernetes.client' 2026-06-12 163140,710 [main] INFO i.m.r.Micronaut(start):183 - No embedded container found. Running as CLI application 2026-06-12 163143,528 [pool-3-thread-1] INFO i.a.c.i.LineGobbler$Companion(gobble$lambda$1):108 - 2026-06-12 163143,530 [pool-2-thread-1] INFO i.a.c.HeartbeatMonitor$HeartbeatTask(run):92 - Transitioning workload to running state 2026-06-12 163144,033 [main] INFO i.a.c.ConnectorWatcher(processConnectorOutput):154 - Connector exited, processing output 2026-06-12 163144,603 [pool-3-thread-1] INFO i.a.c.i.LineGobbler$Companion(gobble$lambda$1):108 - ----- START DISCOVER ----- 2026-06-12 163144,603 [main] INFO i.a.c.ConnectorWatcher(getConnectorOutputStream):191 - Output file jobOutput.json found 2026-06-12 163144,604 [pool-3-thread-1] INFO i.a.c.i.LineGobbler$Companion(gobble$lambda$1):108 - 2026-06-12 163144,605 [main] INFO i.a.c.ConnectorWatcher(processConnectorOutput):157 - Connector exited with exit code 1 2026-06-12 163144,610 [main] INFO i.a.w.i.VersionedAirbyteStreamFactory(create):121 - Reading messages from protocol version 0.2.0 2026-06-12 163144,701 [main] ERROR i.a.w.i.VersionedAirbyteStreamFactory(internalLog$io_airbyte_airbyte_commons_worker):242 - generator raised StopIteration Traceback (most recent call last): File "/airbyte/integration_code/source_mixpanel/components.py", line 266, in extract_records properties = next(super().extract_records(response)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ StopIteration The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/bin/source-mixpanel", line 6, in module sys.exit(run()) ^^^^^ File "/airbyte/integration_code/source_mixpanel/run.py", line 55, in run launch(source, _args) File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/entrypoint.py", line 341, in launch for message in source_entrypoint.run(parsed_args): File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/entrypoint.py", line 163, in run yield from map( File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/entrypoint.py", line 230, in discover catalog = self.source.discover(self.logger, config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/concurrent_declarative_source.py", line 172, in discover concurrent_streams, synchronous_streams = self._group_streams(config=config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/concurrent_declarative_source.py", line 303, in _group_streams declarative_stream.get_json_schema(), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/declarative_stream.py", line 170, in get_json_schema return self._schema_loader.get_json_schema() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/schema/dynamic_schema_loader.py", line 135, in get_json_schema retrieved_record = next(self.retriever.read_records({}), None) # type: ignore[call-overload] # read_records return Iterable data type ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/retrievers/simple_retriever.py", line 540, in read_records for stream_data in self._read_pages(record_generator, self.state, _slice): File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/retrievers/simple_retriever.py", line 374, in _read_pages for record in records_generator_fn(response): File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/retrievers/simple_retriever.py", line 626, in _parse_records yield from self._parse_response( File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/retrievers/simple_retriever.py", line 281, in _parse_response yield from self.record_selector.select_records( File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/extractors/record_selector.py", line 88, in select_records yield from self.filter_and_transform( File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/extractors/record_selector.py", line 119, in filter_and_transform for data in normalized_data: File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/extractors/record_selector.py", line 132, in _normalize_by_schema yield from records File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/extractors/record_selector.py", line 157, in _transform for record in records: File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/declarative/extractors/record_selector.py", line 149, in _filter yield from records RuntimeError: generator raised StopIteration 2026-06-12 163144,706 [main] INFO i.a.c.ConnectorMessageProcessor(updateConfigFromControlMessage):280 - Checking for optional control message... 2026-06-12 163144,711 [main] INFO i.a.c.ConnectorWatcher(saveConnectorOutput):202 - Writing output of 9fbecfaa-a6dd-4b1f-a91c-f47ea6539381_4595e8de-efd1-41f5-af3e-54c84c8e4e4a_0_discover to the doc store 2026-06-12 163144,822 [pool-2-thread-1] INFO i.a.c.HeartbeatMonitor$HeartbeatTask(run):94 - Workload successfully transitioned to running state 2026-06-12 163144,967 [main] INFO i.a.c.ConnectorWatcher(markWorkloadSuccess):207 - Marking workload 9fbecfaa-a6dd-4b1f-a91c-f47ea6539381_4595e8de-efd1-41f5-af3e-54c84c8e4e4a_0_discover as successful 2026-06-12 163144,982 [main] INFO i.a.c.ConnectorWatcher(exitProperly):265 - Deliberately exiting process with code 0. 2026-06-12 163144,982 [pool-5-thread-1] INFO i.a.c.i.LineGobbler$Companion(gobble$lambda$1):108 - 2026-06-12 163144,983 [pool-5-thread-1] INFO i.a.c.i.LineGobbler$Companion(gobble$lambda$1):108 - ----- END DISCOVER ----- 2026-06-12 163144,984 [pool-5-thread-1] INFO i.a.c.i.LineGobbler$Companion(gobble$lambda$1):108 - • Our access creds are correct (Service account and Secret Key) • Project ID is correct • Access is Admin • We have data in Mixpanel

Mixpanel Discovery Error: generator raised StopIteration Your logs show the exact same

RuntimeError: generator raised StopIteration

error that has been reported as a known regression in the Mixpanel source connector. [GitHub Issue] What's happening During schema discovery (the step that runs when you create a connection), the connector fails in

components.py

at:

properties = next(super().extract_records(response))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
StopIteration

This causes the discovery to exit with code 1, producing no catalog — hence the "No catalog found in source discovery output" error you see in the UI. Root cause This is a known regression introduced after connector version 3.5.4, affecting versions 3.6.0 and 3.6.1. The issue was reported as fixed in version 3.6.3. [GitHub Issue] Recommended fix Upgrade your Mixpanel source connector to the latest version (3.6.3 or newer). To do this in Airbyte: 1. Go to Sources and open your Mixpanel source. 2. Look for an upgrade/version option and update to the latest available version. 3. Re-run the connection setup (schema discovery). If you are pinned to a specific connector image version in your Kubernetes deployment, update the image tag to pull the latest

source-mixpanel

connector image. If the issue persists after upgrading • Verify your credentials are still valid (Service Account username + secret). • Check if your Mixpanel project has data accessible via the API. • If still failing on the latest version, consider filing a new GitHub issue with updated logs. [GitHub Issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai, I tried 3.5.0 version and it showed streams. Problem is that I have started synced 14 hours back and when I logged in to Airbyte it was still syncing. Same "funnels" stream was syncing

Mixpanel Sync Hanging on Funnels Stream This is a known performance issue with the Mixpanel connector. Based on the knowledge sources, here's what's likely happening: Root Cause The

MixpanelStream

base class enforces a 60-second sleep between every API request to respect Mixpanel's rate limit of 60 queries/hour:

if self.reqs_per_hour_limit > 0:
    self.logger.info(f"Sleep for {3600 / self.reqs_per_hour_limit} seconds ...")
    time.sleep(3600 / self.reqs_per_hour_limit)

This means every single paginated request waits 60 seconds, which can cause syncs with large datasets to take many hours. [Mixpanel streams.py] A similar issue was confirmed for the

engage

stream — a fix reduced sync time from 11 hours to ~26 minutes by disabling the unnecessary sleep on pagination requests. [GitHub Issue] What You Can Do Now 1. Reduce the date window — In your Mixpanel source settings, set a smaller Date slicing window and use a more recent start date to limit the amount of data being synced. [Performance Considerations] 2. Disable the Funnels stream if you don't need it — Funnels uses the Query API which has stricter limits (5 concurrent queries, 60/hour). [Performance Considerations] 3. Try a newer connector version — The 60-second sleep issue has been acknowledged and partially addressed in newer versions. The version 3.5.0 you're using is relatively old; consider trying 3.5.4 (the last known stable version before the discovery regression). 4. Cancel and retry with a narrower date range — Users in similar situations found that canceling and retrying with a shorter sync window helped complete the sync successfully. [Forum Post] > ⚠️ The knowledge sources do not contain specific details about fixes targeting the Funnels stream's sleep behavior specifically, so I cannot confirm whether a particular newer version fully resolves this for Funnels. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

how much should be data slicing window @kapa.ai

Recommended Date Slicing Window The knowledge sources do not provide a single definitive "best" value, but here's what is documented: • The default is 30 days per request window. [Mixpanel Setup Guide] • The docs explicitly recommend: reduce this value if you encounter memory issues or large volumes of data per window. [Mixpanel Setup Guide] Practical Guidance for Your Situation Since you're experiencing long-running syncs on the Funnels stream, consider reducing the window significantly: Key Trade-off to Keep in Mind A smaller window means: • ✅ Less data per request (less memory pressure) • ✅ Easier to recover if a sync fails mid-way • ❌ More total API requests, and since each request has a ~60-second sleep enforced by the rate limiter, a smaller window can paradoxically increase total sync time So for your case with the hanging Funnels stream, I'd suggest trying 14 days as a balance — small enough to avoid memory issues but not so small that it multiplies the number of rate-limited requests excessively. > ⚠️ The knowledge sources do not contain benchmark data for the Funnels stream specifically, so treat these as starting-point recommendations rather than guaranteed values. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements