[APM] "The selected trace can not be found" error in Kibana on sampled trace from Latency Distribution graph

[liladler]

Versions
Kibana: 7.11.2
APM Server: 7.11.2
Elasticsearch: 7.11.2
APM agent: Python agent v6

When clicking in the APM “Latency Distribution” graph and later in the “Trace Sample” section underneath it, we get The selected trace can not be found error as shown in the following screenshot -

• We are sampling all transactions therefore all traces should be present.
• We are seeing s exceedsMax=true header in the response.
• We tried different browsers and got the same result.
• Response code is 200.
• We are seeing traces data in the response using browser's inspect.
• There are no write rejects from the cluster so it doesn't seem to be related to ingestion.
• Kibana resources are 8GB of RAM and doesn't seem to be loaded.

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[sorenlouv]

This logic was changed in #99905 and is expected to be fixed by 7.15. Please comment to re-open this if this continues to be an issue.