Open FionaYiZhao opened 3 years ago
+1
We have also been seeing errors. In general, we've always seen a range of errors from this tap for the DataExtension table replications, however, the sync was generally able to complete. However, starting on the 14th, these errors caused the entire sync to die prematurely. We've had to not replicate our DataExtension tables to get the sync to complete. To our knowledge, nothing has changed with in the Marketing Cloud account.
actually the error came back. but I do see tables got updated in our BQ destination..
On Fri, Sep 17, 2021 at 1:20 PM Robert Shedd @.***> wrote:
We have also been seeing errors. In general, we've always seen a range of errors from this tap for the DataExtension table replications, however, the sync was generally able to complete. However, starting on the 14th, these errors caused the entire sync to die prematurely. We've had to not replicate our DataExtension tables to get the sync to complete. To our knowledge, nothing has changed with in the Marketing Cloud account.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singer-io/tap-exacttarget/issues/69#issuecomment-921958090, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARN5BL42X4KKRWSTH6HAPNTUCN2GTANCNFSM5EHJX4UA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
We've just started replicating tables from SFMC using Stitch, and running into a similar issue. The latest email from Stitch regarding errors had a blank space where the error should be ...
We're not replicating any of the data_extension tables but still see data_extension referenced in the logs - is that normal?
Some tables are replicating into our warehouse, but not the email
or campaign
tables, and I've been unable to identify the cause. Looks like there aren't any known workarounds for this?
@FionaYiZhao and @shedd: Are you still facing this issue?
We are still facing this issue.
Additionally we started getting a a new error today as well:
Full logs:
2022-12-07 21:57:01,781Z tap - CRITICAL 'metadata'
2022-12-07 21:57:01,785Z tap - Traceback (most recent call last):
2022-12-07 21:57:01,785Z tap - File "tap-env/bin/tap-exacttarget", line 33, in <module>
2022-12-07 21:57:01,785Z tap - sys.exit(load_entry_point('tap-exacttarget==1.7.1', 'console_scripts', 'tap-exacttarget')())
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/singer/utils.py", line 229, in wrapped
2022-12-07 21:57:01,786Z tap - return fnc(*args, **kwargs)
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/tap_exacttarget/__init__.py", line 168, in main
2022-12-07 21:57:01,786Z tap - do_discover(args)
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/tap_exacttarget/__init__.py", line 70, in do_discover
2022-12-07 21:57:01,786Z tap - catalog += stream_accessor.generate_catalog()
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/tap_exacttarget/endpoints/data_extensions.py", line 229, in generate_catalog
2022-12-07 21:57:01,786Z tap - extensions_catalog_with_fields = self._get_fields(extensions_catalog)
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/backoff/_sync.py", line 94, in retry
2022-12-07 21:57:01,786Z tap - ret = target(*args, **kwargs)
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/tap_exacttarget/dao.py", line 44, in wrapper
2022-12-07 21:57:01,786Z tap - return fnc(*args, **kwargs)
2022-12-07 21:57:01,786Z tap - File "/code/orchestrator/tap-env/lib/python3.5/site-packages/tap_exacttarget/endpoints/data_extensions.py", line 187, in _get_fields
2022-12-07 21:57:01,786Z tap - to_return[extension_id]['metadata'].append({
2022-12-07 21:57:01,786Z tap - KeyError: 'metadata'
2022-12-07 21:57:02,467Z main - INFO Tap exited abnormally with status 1
2022-12-07 21:57:03,878Z main - INFO [smart-services] event successfully sent to kafka: com.stitchdata.extractionJobFinished [42] at offset None
2022-12-07 21:57:03,883Z main - INFO No tunnel subprocess to tear down
2022-12-07 21:57:03,883Z main - INFO Exit status is: Discovery failed with code 1 and error message: "'metadata'".
Hi team,
Our SFMC extract was reported in error states for many days. This morning it turned to normal, we didn't actually do or change anything. We are trying to understand the cause of the errors. Could anybody help here? Attached is one of the log (truncated some middle session):