-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LinkedIn Ads Source hangs after preparing tmp Tables #7206
Comments
i tested the source and the docker image for it locally. the issue doesn't seem to be in the source connector. for the testing i created a config.json with the credentials and tested the docker container as explained here under Edit: |
@tinomerl apologies for the late response here! will look into this and understand the root cause soon. Are you open to sharing the full job logs with us by downloading it from the UI? |
@sherifnada thanks for the reply! i added some logs specific for this source and destination in the issue when i opened it under |
@tinomerl would you be able to share the full logs? specifically i'm unable to tell how this job terminated -- was it cancelled manually or failed on its own? |
@sherifnada i cancelled the job manually after the message Before that it ran for almost 20 Minutes without syncing any data. i attached the whole log. Is this sufficient? Full Logs
|
thanks, this is helpful! |
@tinomerl @sherifnada this error was caused due to rate limits. Each account has quota limits for requests. Rate limits specify the maximum number of API calls that can be made in a 24 hour period. These limits reset at midnight UTC every day. You can find more information here. Also quotas and usage are here. Also, just published a new connector version with a more informative log message, when sync is stopped. |
Hey @annalvova05 thanks for your comment. But the issue seems to be a different one. I upgraded to your connector version last week and tested it. It took about 2 Hours to replicate the data to postgres. This is the only source connector we have problems with. I also checked our quotas after you mentioned it. We don't run into any restrictions here either. @sherifnada i attached the logs to the original comment and updated the connector version. Could the issue please be reopened? |
Enviroment
Current Behavior
When replicating data from LinkedIn Ads to Postgres the tmp tables will be prepared but afterwards nothing happens. The Sync Job hangs and won't call any data. After some time a retryable Error is caught.
Expected Behavior
Data from LinkedIn should be replicated.
I tested different sources to exclude it's because of the deployment. I also tested with LinkedIn as a source and other destinations. No change in behaviour. Also tested in two different environments.
Logs
LinkedIn Ads to Postgres
LinkedIn 0.1.4 to Postgres
Steps to Reproduce
Acceptance Criteria
Caught retryable error ''
which doesn't tell us what the actual error wasAre you willing to submit a PR?
Yes
The text was updated successfully, but these errors were encountered: