@kapa.ai we were trying to pull the google analytics using the airbyte, we have added 7 to 8 propertyIds in the source but when we were trying to create connection, why the stream name is ending with property<propertyId> also only 1 ID is populating that pattern. is it possible to remove that and get all data in one stream itself?

Thinking completed Why stream names end with PropertypropertyId and only show one ID By default, the Google Analytics 4 (GA4) connector creates a separate stream for every combination of report and Property ID [One Stream per Report]. Stream naming follows a backward-compatible convention [Unique Behaviors]: • The first Property ID in your list uses the plain report name (for example,

content_group_report

). • Each additional Property ID gets a

Property<propertyId>

suffix appended (for example,

content_group_reportProperty317098489

). In your screenshot, only two streams per report appear because only two Property IDs were recognized or configured during schema discovery. If you added 7–8 IDs in the source settings, ensure that your source settings were saved and that you refreshed the connection schema [One Stream per Report]. Otherwise, by default, it would list one stream for the first ID and an additional

Property<propertyId>

stream for each of the remaining 6–7 IDs [One Stream per Report; Unique Behaviors]. Is it possible to get all data into one stream? Yes. You can merge all properties into a single stream per report by enabling One Stream per Report in the source configuration [One Stream per Report]. When this setting is enabled: • The connector creates one stream per report covering all configured Property IDs [One Stream per Report]. • Streams are renamed with a

Consolidated

suffix (for example,

devices

becomes

devicesConsolidated

,

content_group_report

becomes

content_group_reportConsolidated

) [One Stream per Report]. • The per-property streams (

<report>

and

<report>Property<id>

) are removed [One Stream per Report]. • Each record automatically includes a

property_id

column, which is part of the stream's primary key so rows from different properties stay distinct in your destination table [One Stream per Report]. How to set it up: 1. Go to your GA4 Source Settings in Airbyte, enable One Stream per Report (or

single_stream_per_report

), and save [One Stream per Report]. 2. Go to your Connection and click Refresh source schema [One Stream per Report]. 3. You will see the old streams removed and replaced by

<report_name>Consolidated

streams [One Stream per Report]. 4. Enable the consolidated streams you want and sync your connection [One Stream per Report]. 👍 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 how can I enable one stream per report, in the UI I am not able to see the option to toggle

Thinking completed I'm sorry, but the provided knowledge sources do not explicitly explain where the toggle is located in the UI or why it might not be visible in your version of the interface. However, based on the available documentation and connector code, here is what is known: 1. Connector Configuration Field: The setting is configured at the source level (under the source's configuration settings, rather than on the connection schema page) and corresponds to the configuration key

single_stream_per_report

[One Stream per Report; dynamic_streams]. 2. Connector Version: This feature was added recently. If you do not see the One Stream per Report option when editing your Source configuration (under Sources > select your GA4 source > Settings), your Airbyte instance may be running an older version of the

source-google-analytics-data-api

connector. Upgrading the GA4 source connector to the latest version in the Airbyte Connector Builder/Settings may be required to expose the toggle. 👍 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 message='Airbyte could not start the process within time limit. The workload was claimed but never started.', type='io.airbyte.workers.exception.WorkloadMonitorException', nonRetryable=false

Thinking completed This error is generated by Airbyte's Workload Monitor background process [Workload Monitor]. What This Error Means The Workload Monitor watches workloads through their lifecycle [Workload Monitor]. The message: >

"Airbyte could not start the process within time limit. The workload was claimed but never started."

means that the workload was placed into a

CLAIMED

status by the Workload Launcher, but it failed to transition to

LAUNCHED

or

RUNNING

before its deadline expired [Workload Monitor]. Likely Causes • Kubernetes Pod Launch Failures: The launcher claimed the job but encountered Kubernetes API errors or resource limits when attempting to create the pod [Workload Monitor]. • Cluster Resource Constraints: The cluster lacks sufficient CPU or memory to satisfy the pod's resource requests, leaving it unschedulable [Workload Monitor]. • Pod Lifecycle Issues: The pod could be stuck in

Pending

,

CrashLoopBackOff

,

ImagePullBackOff

, or was terminated due to being

OOMKilled

[Workload Monitor]. Recommended Debugging Steps To diagnose why the pod did not start in Kubernetes [Workload Monitor]: 1. *Check pod status:*kubectl get pods -n namespaceLook for pods in

Pending

,

CrashLoopBackOff

,

ImagePullBackOff

, or

OOMKilled

states [Workload Monitor]. 2. *Inspect pod events:*kubectl describe pod pod-name -n namespaceReview the events section at the bottom for scheduling failures, resource pressure, or image pull issues [Workload Monitor]. 3. *Check pod logs:*kubectl logs pod-name -n namespace -c container-nameLook for container startup errors or uncaught exceptions [Workload Monitor]. 4. Review cluster resources: Ensure the Kubernetes cluster has enough unallocated CPU and memory available to satisfy the pod's resource requests [Workload Monitor]. 👍 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 'GET' request to 'googleapis.com/calendar/…/events' failed with status code '404' and error message: 'Not Found'. Request (body): 'None'. Response (body): '{'error': {'errors': [{'domain': 'global', 'reason': 'notFound', 'message': 'Not Found'}], 'code': 404, 'message': 'Not Found'}}'. Response (headers): '{'Cache-Control': 'no-cache, no-store, max-age=0, must-revalidate', 'Date': 'Fri, 16 Oct 2026 154133 GMT', 'Content-Type': 'application/json; charset=UTF-8', 'Pragma': 'no-cache', 'Expires': 'Mon, 01 Jan 1990 000000 GMT', 'Vary': 'Origin, X-Origin, Referer', 'Content-Encoding': 'gzip', 'Server': 'ESF', 'X-XSS-Protection': '0', 'X-Frame-Options': 'SAMEORIGIN', 'X-Content-Type-Options': 'nosniff', 'x-l2-request-path': 'l2-managed-14', 'Transfer-Encoding': 'chunked'}'. I am getting this 404 error for Google Calender

Thinking completed This 404 means the Google Calendar API could not find the calendar configured in Calendar Id. The connector classifies a 404 as a config error with this message: "The calendar configured in "Calendar Id" was not found by the Google Calendar API. Check the ID in the calendar's settings, or use 'primary'." [Error handler] Your request went to

calendars/jeremy.h@datagol.ai/events

, so the configured Calendar Id is

jeremy.h@datagol.ai

. What to check 1. Calendar Id value: Confirm it matches the ID in the calendar's settings in Google Calendar. For the primary calendar, this is the account's email address. [Config spec] 2. Account mismatch: The email must belong to the Google account that generated your OAuth refresh token, or to a calendar that account can access. The knowledge sources don't explicitly cover this case. It's a likely cause, since the connector can only see calendars available to the authorized account. 3. Try the

primary

alias:

primary

also works. It is stored verbatim in

events.calendar_id

, so it won't join to

calendarlist.id

or

calendars.id

. [Events sync behavior] 4. Check for typos or extra whitespace in the ID. Other statuses are handled differently. A 403 means the account lacks access to the calendar or the Calendar API is disabled, and a 401 means the OAuth credentials were rejected. [Error handler] If the problem persists after these checks, the knowledge sources don't contain enough information to diagnose it further. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.