#7359 bug: install telemetry exit events are sometimes missing Issue created by pnadolny13 Meltano Version 2.16.1 Python Version 3.9 Bug scope CLI (options, error messages, logging, etc.) Operating System Cloud Description It looks like in some cases during a

meltano install

we're only getting the started event, then nothing else so we dont know how long the install took. I was noticed this because I saw cli runtime at 0 for many recent Squared jobs running in Meltano cloud. Things I looked into before I opened this: • It doesnt look like anything special is happening in https://github.com/meltano/infra/blob/main/deployments/cloud/durable_shared_resources/docker/meltano/entry.sh, just a

meltano install

• I didnt see anything obvious in the code that looked like it could cause this meltano/src/meltano/cli/install.py Line 45 in</meltano/meltano/commit/b1f65b713a2a1975655a7ee3f345bbf180455288|b1f65b7> | def install( | | ------------ | • I explored if this was happening for a particular meltano verison but it seems to be present (in small quantities) in most all versions and no real trend was present. • I looked at snowplow raw events in case my dbt models were parsing them incorrectly. No events were missing there. • I looked at snowplow schema failure events to see if they were in the "bad" bucket but nothing there either. I did notice that when Squared got put onto Cloud it immediately starts happening. I dont see others on cloud having this issue so it might be isolated but still very strange. Squared was previously opted out of telemetry before cloud, I cant imagine thats related but who knows 🤷 . @WillDaSilva Any idea why this could be happening? Code No response meltano/meltano