Summary:

Customers using the Assembled connector would like the ability to control the return_full_schedule parameter in the GET /v0/activities API call. Currently, the connector always uses return_full_schedule=true, which causes the connector to ingest the full activity “stack,” resulting in overlapping and duplicate activity events.

Current Behavior

• The Assembled connector is hard-coded to call GET /v0/activities with return_full_schedule=true

• Because of that the full schedule is always returned, customers cannot choose to ingest only the effective activity events.

Customer Impact

• Customers receive overlapping/duplicate activity records, which must be manually filtered or transformed downstream.

• Some customers are only interested in the effective schedule and do not need the full layered activity set.

Requested Enhancement

• Add a connector-level configuration option that allows customers to set return_full_schedule=false when desired.

• This would enable ingestion of only the effective, non-overlapping activity events.