[source-auth0] 'Cannot attempt to connect to stream organization_member_roles - no stream slices were found, likely because the parent stream is empty.' - Githubissues

airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.

https://airbyte.com

Other

16.07k stars 4.11k forks source link

[source-auth0] 'Cannot attempt to connect to stream organization_member_roles - no stream slices were found, likely because the parent stream is empty.' #45874

Open Dmytro4343434 opened 1 month ago

Dmytro4343434 commented 1 month ago

Connector Name

Auth0

Connector Version

0.6.0

What step the error happened?

Configuring a new connector

Relevant information

No response

Relevant log output

2024-09-24 10:53:53 [32mINFO[m i.a.c.ConnectorWatcher(processConnectorOutput):114 - Connector exited, processing output
2024-09-24 10:53:53 [32mINFO[m i.a.c.i.LineGobbler(voidCall):166

Contribute

[ ] Yes, I want to contribute

marcosmarxm commented 1 month ago

@Dmytro4343434 can you share the complete sync log?

Dmytro4343434 commented 1 month ago

@marcosmarxm unfortunately, there is nothing else

alexhwoods commented 3 weeks ago

I just got this issue as well - I think the Auth0 Marketplace source may be broken

alexhwoods commented 3 weeks ago

Here's my theory - we do not use "Organizations" in Auth0. We just use "Users".

I think there is a dependency on the user of the Auth0 source using "Organizations" written into the connector. A join instead of a left join, if that makes sense.

stephenhuh commented 2 weeks ago

seems that the auth0 connector doesn't work for most scenarios in its current state. this was done via the oAuth2 Access Token since the Confidential Application flow wasnt working either and seems to have quite a few issues here related to it.

@marcosmarxm i've added some logs here that i received:

2024-10-20 00:05:50 platform > 
2024-10-20 00:05:50 platform > Connector exited, processing output
2024-10-20 00:05:50 platform > ----- START CHECK -----
2024-10-20 00:05:50 platform > Output file jobOutput.json found
2024-10-20 00:05:50 platform > 
2024-10-20 00:05:50 platform > Connector exited with exit code 0
2024-10-20 00:05:50 platform > Reading messages from protocol version 0.2.0
2024-10-20 00:05:50 platform > MetricClient has not been initialized. Must call MetricClientFactory.CreateMetricClient before using MetricClient. Using a dummy client for now. Ignore this if Airbyte is configured to not publish any metrics.
2024-10-20 00:05:50 platform > Successfully connected to stream organizations, but got 0 records.
2024-10-20 00:05:50 platform > Check failed
2024-10-20 00:05:50 platform > Checking for optional control message...
2024-10-20 00:05:50 platform > Optional control message not found. Skipping...
2024-10-20 00:05:50 platform > Writing output of 6c504e48-14aa-4221-9a72-19cf5ff1ae78_ffd9e225-41e4-4a6f-b5b7-c004e30b3aff_0_check to the doc store
2024-10-20 00:05:50 platform > Marking workload 6c504e48-14aa-4221-9a72-19cf5ff1ae78_ffd9e225-41e4-4a6f-b5b7-c004e30b3aff_0_check as successful
2024-10-20 00:05:50 platform > 
2024-10-20 00:05:50 platform > Deliberately exiting process with code 0.
2024-10-20 00:05:50 platform > ----- END CHECK -----

to others reading i don't think this connector is close to stable yet.