Jens Mostaert
07/17/2025, 11:28 AMPOST /api/v1/sources/update
{
"message": "Internal Server Error: io.grpc.StatusRuntimeException: ALREADY_EXISTS: Secret [projects/332657581931/secrets/airbyte_workspace_67db3dcd-eb80-424c-9ae2-e42d654f28bc_secret_78eadfdf-dde2-45e9-b287-d3f37b8c5ee3_v7084] already exists.",
"exceptionClassName": "com.google.api.gax.rpc.AlreadyExistsException",
"exceptionStack": [],
"rootCauseExceptionStack": []
}
Martin Andonov
07/17/2025, 6:54 PMLorenzo
07/17/2025, 10:21 PMPaul Houghton
07/18/2025, 12:52 PMMukesh Kumar
07/19/2025, 5:18 AMBilal Mubasher
07/21/2025, 8:48 AMBilal Mubasher
07/21/2025, 8:57 AMBilal Mubasher
07/21/2025, 1:33 PMRafael Capelo
07/21/2025, 5:59 PMLorenzo
07/23/2025, 4:02 AMGergely Imreh
07/23/2025, 7:33 AM2025-06-01
, and from there I have to run requests with the query parameters: from_date
set to 2025-06-01
and the to_date
set to 2025-06-02
; after this I have to query again, but setting 2025-06-02
and 2025-06-03
, and so on up until today
• is this possible with incremental sync (if there's no cursor on the API, but it would keep its own "up to this date" value? (this would be the best, probably, meaning fastest sync)
• or, is it possible through the possible though pagination?
Or would I need to built a more custom connector for this?
Cheers!Rubén Laguna
07/24/2025, 7:34 AMAnder Aranburu
07/25/2025, 7:59 AMState message does not contain idIf anyone is familiar with how/why this issue arises, I’d really appreciate your insight. A few specific questions I’m trying to figure out: • Was this issue introduced by a recent change in the Airbyte Protocol or CDK? • Is it related to the source connector at all, or only to how the destination handles state messages? • Why don’t other destinations using CDK 6.x (e.g. destination-sqlite) seem to be affected? Thanks in advance for any help you can share! 🙏
Alexei Kozhushkov
07/25/2025, 9:05 AMairbyte
install and it works great with mysql, mssql and postgres.
But I can't make connector builder
to work, e.g. even simples unauthenticated <https://restcountries.com/v3.1/all?fields=name>
fails with Draft can't be saved
error.
Please advise 🙏Michael Hernandez
07/25/2025, 5:28 PMissue_remote_links
only supports full_refresh which makes sense as Atlassian didn't include a date or ID column that could be used for incrementally syncing.
If I could use the keys from the issues
stream sync, I could achieve something similar by fetching only for particular issues.Alex Johnson
07/26/2025, 12:55 AMAlexei Kozhushkov
07/29/2025, 9:41 AMDpathExtractor
yaml config:
• Given following array as input
[{
"name": {
"common": "Comoros",
"official": "Union of the Comoros",
"nativeName": {
"ara": {
"official": "الاتحاد القمري",
"common": "القمر"
},
"fra": {
"official": "Union des Comores",
"common": "Comores"
},
"zdj": {
"official": "Udzima wa Komori",
"common": "Komori"
}
}
},
"cca2": "KM",
"cca3": "COM"
}]
• how would one extract
[{
"name": { "common": "Comoros" },
"common_name": "Comoros",
"cca2": "KM",
"cca3": "COM"
}]
Please advise 🙏Olivia Natasha
07/29/2025, 3:51 PMMohith
07/31/2025, 9:46 AMARRAY
data type in our PostgreSQL source are being read as strings when synced to our Snowflake destination using the PostgreSQL connector.
Is this expected behavior? If not, could anyone familiar with the PostgreSQL connector share how they’ve handled array-type columns in similar setups?
Any insights or suggestions would be greatly appreciated.
Thanks in advance!Prajjval Mishra
07/31/2025, 6:11 PMAlexei Kozhushkov
08/01/2025, 7:21 AMMorgan Kerle
08/05/2025, 12:27 AMAlexei Kozhushkov
08/05/2025, 9:17 AM<https://allegro.pl/auth/oauth/authorize?response_type=code&client_id=a21...6be&redirect_uri=http://exemplary.redirect.uri>
• Token
curl -X POST \
<https://allegro.pl/auth/oauth/token> \
-H 'Authorization: Basic base64(clientId:secret)' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'grant_type=authorization_code&code=pOPEy9Tq94aEss540azzC7xL6nCJDWto&redirect_uri=<http://exemplary.redirect.uri>'
Thank you!Grivine Ochieng'
08/05/2025, 2:54 PM{
"url": "<https://backstage.taboola.com/backstage/api/1.0/sinoinc-nal-plaudus-sc/reports/campaign-summary/dimensions/day?start_date=2025-01-01&end_date=2025-08-05>",
"headers": {
"User-Agent": "python-requests/2.32.4",
"Accept-Encoding": "gzip, deflate",
"Accept": "*/*",
"Connection": "keep-alive",
"Authorization": "Bearer ****"
},
"http_method": "GET",
"body": ""
}
Response payload:
{"status": 200,
"body": {
"last-used-rawdata-update-time": "2025-08-05 05:00:00.0",
"last-used-rawdata-update-time-gmt-millisec": 1754395200000,
"timezone": "PDT",
"results": [
{
"date": "2025-08-05 00:00:00.0",
"date_end_period": "2025-08-05 00:00:00.0",
"clicks": 628,
"impressions": 271757,
"visible_impressions": 147123,
"spent": 105.26,
"conversions_value": 0,
"roas": 0,
"roas_clicks": 0,
"roas_views": 0,
"ctr": 0.2310888036002752,
"vctr": 0.4268537210361398,
"cpm": 0.39,
"vcpm": 0.72,
"cpc": 0.168,
"campaigns_num": 20,
"cpa": 6.192,
"cpa_clicks": 6.579,
"cpa_views": 105.264,
"cpa_actions_num": 17,
"cpa_actions_num_from_clicks": 16,
"cpa_actions_num_from_views": 1,
"cpa_conversion_rate": 2.7070063694267517,
"cpa_conversion_rate_clicks": 2.5477707006369426,
"cpa_conversion_rate_views": 0.1592356687898089,
"currency": "USD"
},
Carmela Beiro
08/05/2025, 3:54 PMsource-declarative-manifest
as the base and copying the manifest.yaml generated with the Custom Builder UI? Can't find documentation about itMateo Colina
08/05/2025, 6:27 PMSebastian Miranda
08/07/2025, 8:25 PMPatrick McCoy
08/11/2025, 4:12 PMOfek Eliahu
08/12/2025, 2:46 PM{
"access_token": "c97d1fe52119f38c7f67f0a14db68d60caa35ddc86fd12401718b649dcfa9c68",
"token_type": "bearer",
"expires_in": 7200,
"refresh_token": "803c1fd487fec35562c205dac93e9d8e08f9d3652a24079d704df3039df1158f",
"created_at": 1628711391
}
To re-authenticate, I need to use the new refresh token from the response. I’m using the SingleUseRefreshTokenOauth2Authenticator
to handle this, which saves the new refresh_token
, access_token
, and expire_time
in memory for the next authentication.
The issue is that while these config values are correctly saved and used in memory, they are not being persisted in storage for future runs. When I create a new source, a validation check is performed, which passes and creates the source. However, after this check, the OAuth refresh token becomes invalid, and the new one isn’t saved to storage. As a result, I can’t create a new connection based on this source since the refresh token isn’t being updated in storage.
Is anyone faced this issue before and knows how to solve it?Will Skelton
08/12/2025, 3:30 PM