<@U04S8PLJWMT> I am getting this issue "externalMe...
# replication-ask-ai
s
@kapa.ai I am getting this issue "externalMessage" : "During the sync, the following streams did not sync successfully: average_session_length: MessageRepresentationAirbyteTracedErrors(\"'GET' request to 'https://amplitude.com/api/2/sessions/average?start=20250401&end=20250415' failed with status code '403' and error message: 'Date too far back'. Request (body): 'None'. Response (body): '{'error': {'http_code': 403, 'type': 'date restricted', 'message': 'Date too far back', 'metadata': {'details': '2025-04-01 is before cutoff date of 2025-04-02', 'cutoff_date': '2025-04-02'}}}'. Response (headers): '{'Date': 'Fri, 03 Apr 2026 123048 GMT', 'Content-Type': 'application/json; charset=UTF-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'server-timing': 'dash;dur=113.7', 'x-amzn-trace-id': 'Root=1-69cfb2f8-15ab9eea15302ea21ebbc303', 'x-content-type-options': 'nosniff', 'cache-control': 'no-cache, no-store, must-revalidate', 'pragma': 'no-cache', 'expires': '0', 'content-encoding': 'gzip', 'strict-transport-security': 'max-age=31536000; includeSubDomains; preload;', 'x-frame-options': 'SAMEORIGIN', 'set-cookie': 'SERVERID=; Expires=Thu, 01-Jan-1970 000001 GMT; path=/'}'.\")",
k
The error you're encountering is a 403 "Date too far back" response from Amplitude's API. This means the
start
date you're requesting (
2025-04-01
) is before Amplitude's data retention cutoff date (
2025-04-02
). This is a data retention limitation enforced by Amplitude's API — they do not allow querying data older than their cutoff date. What you can do 1. Update your Replication Start Date: In your Airbyte connection settings for the Amplitude source, update the Replication Start Date to a date that is within Amplitude's retention window (i.e., on or after the cutoff date). [Amplitude connector docs] 2. Check Amplitude's data retention policy: Amplitude enforces retention limits on their Dashboard REST API (which the
average_session_length
stream uses). If your configured start date falls before the cutoff, the sync will fail with this 403 error. Additional context The
average_session_length
stream uses Amplitude's Dashboard REST API endpoint
/2/sessions/average
. The knowledge sources note that Amplitude's Export API and Dashboard REST API have different behaviors and limitations. [source-amplitude contributing] Unfortunately, the knowledge sources do not describe a built-in mechanism in the Airbyte Amplitude connector to automatically skip dates before the cutoff. The recommended fix is to manually adjust your start date in the connector configuration to be within Amplitude's allowed retention window. šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
This is the same error as in your previous message — a 403 "Date too far back" from Amplitude's Dashboard REST API, indicating that the requested
start
date (
2025-04-01
) falls before Amplitude's data retention cutoff (
2025-04-02
). The knowledge sources do not describe any automatic mechanism in the Airbyte Amplitude connector to skip or cap dates before Amplitude's cutoff for the
average_session_length
stream (unlike, for example, the Amazon Ads connector which has a built-in date cap). [Amplitude connector docs] Recommended fix Update your Replication Start Date in the Amplitude source connector configuration to a date on or after Amplitude's cutoff date. Based on the error, the cutoff is
2025-04-02
, so setting your start date to
2025-04-02T00:00:00Z
or later should resolve the issue. To do this: 1. Go to your Airbyte workspace → Sources → your Amplitude source. 2. Edit the Replication Start Date field to a date within Amplitude's retention window. 3. Save and re-run the sync. > Note: The
average_session_length
stream uses Amplitude's Dashboard REST API (
/2/sessions/average
), which enforces its own data retention limits. If your connector's cursor state holds an older date, updating the start date in the configuration should override it for the next sync. [source-amplitude contributing] šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
s
is it only for average_sessions_length_stream or all streams @kapa.ai
k
Based on the knowledge sources, the 403 "Date too far back" error due to Amplitude's data retention cutoff is specifically relevant to streams that use the Dashboard REST API, which includes: • Average Session Length (
/2/sessions/average
) • Active Users Counts (also uses the Dashboard REST API) The
average_session_length
and
active_users
streams both use Amplitude's Dashboard REST API and are incremental streams. [source-amplitude contributing] The Events stream, however, uses a different API — Amplitude's Export API — which has different (and largely undocumented) rate limits and behaviors. [source-amplitude contributing] The other streams (Annotations, Cohorts, Events List) are not incremental and do not use date-range parameters in the same way, so they are less likely to be affected by this specific date restriction error. That said, the knowledge sources do not explicitly document Amplitude's retention cutoff policy for each individual stream. I'd recommend checking Amplitude's API documentation for the specific retention limits per endpoint, and ensuring your Replication Start Date is set within the allowed window for all date-range-based streams. šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.