Christian Lam
10/06/2022, 3:19 PM0.39.39
to 0.40.11
and the GA connector is starting to fail with this message:
Additional Failure Information: message='Job ran during migration from Legacy State to Per Stream State. One of the streams that did not have state is: io.airbyte.protocol.models.StreamDescriptor@3dc7762a[name=primary,namespace=<null>,additionalProperties={}]. Job must be retried in order to properly store state.', type='java.lang.IllegalStateException', nonRetryable=false
I tried resetting the connector but that did not make a difference. The sync mode being used is Incremental Deduped + History
.
EDIT: I was able to resolve this issue by manually deleting the state record from the app db.user
10/06/2022, 3:59 PMMarcos Marx (Airbyte)
10/06/2022, 6:28 PMFlorian Melki
10/10/2022, 10:23 AMFlorian Melki
10/10/2022, 10:26 AMFlorian Melki
10/10/2022, 12:27 PMJonas Meier
10/11/2022, 6:47 AMJonas Meier
10/11/2022, 6:50 AMMarcos Marx (Airbyte)
10/11/2022, 11:06 AMŠimon Appelt
10/11/2022, 11:26 AMJonas Meier
10/11/2022, 11:43 AMFlorian Melki
10/11/2022, 12:24 PMMarcos Marx (Airbyte)
10/11/2022, 1:54 PMFlorian Melki
10/11/2022, 2:01 PMFlorian Melki
10/13/2022, 7:36 AMSebastian Brickel
11/08/2022, 12:02 PMJob ran during migration from Legacy State to Per Stream State. One of the streams that did not have state is
I tried deleting the table from my destination (BigQuery) and even reset my data, but nothing helped.
What exactly is meant by
"EDIT: I was able to resolve this issue by manually deleting the state record from the app"
Marcos Marx (Airbyte)
11/08/2022, 6:11 PMSebastian Brickel
11/09/2022, 8:01 AMad_sets
stream that causes the error, when removing it from syncing it then is ads
and afterwards a few other streams that have the wrong state.
I found out that changing the sync mode from Incremental | Deduped + history
to Full refresh | Append
seems to work, but I don’t no whyMarcos Marx (Airbyte)
11/21/2022, 5:51 PMSebastian Brickel
11/22/2022, 8:39 AMIncremental | Deduped + history
but unfortunately now run into facebooks limit for call to ad-accounts.
The strange thing is that his only happens to the three facebook ad acount where I had this issue, all other facebook ad accounts that I sync have no problem with these limits.
It is still a bit strange!
Did you find something in my logs?Marcos Marx (Airbyte)
11/22/2022, 5:14 PMRuntimeError: Batch request failed with response: {'error': {'message': '(#80004) There have been too many calls to this ad-account. Wait a bit and try again. For more info, please refer to <https://developers.facebook.com/docs/graph-api/overview/rate-limiting.>', 'type': 'OAuthException', 'code': 80004, 'error_subcode': 2446079, 'fbtrace_id': 'ANX17jXpw22W_9wKVVIIco_'}}
There isn’t anything meaningful. Are you using same crdentials to run 3 accounts or they use different credentials?Sebastian Brickel
11/23/2022, 7:45 AMSebastian Brickel
11/23/2022, 7:46 AMThere have been too many calls to this ad-account
message is that it also appeared on Monday after I turned of the connector for the weekendMarcos Marx (Airbyte)
11/28/2022, 1:56 PMSebastian Brickel
11/28/2022, 3:09 PMuser
12/01/2022, 5:49 PMSebastian Brickel
12/02/2022, 9:08 AMSebastian Brickel
12/08/2022, 3:11 PM