Vlad S.

I don't know about images, but everything we render inside a canvas in our app doesn't get captured... I don't think it's surprising, since it would probably take a lot more effort to capture all such edge cases and make sure they work correctly

but that's a good idea... it doesn't fully account for the "started job a" -> "completed job b" scenario, but it's close

How many times does an average user do this event?

it's a very long tailed distribution... the average is probably once per week, with a LOT of users not doing it ever and several doing it hundred times a day

might just need to download all the events and parse them offline

easily done going forwards, have no idea how to do it going "backwards"

also, started and completed events have unique IDs that correspond to each job, so ideally I would look for completed jobs that never got started (even if other jobs got started during that time period) by using "hold property constant" and setting it to the unique job id

yeah, I could find the users who never fire the started event when they should, but I'd also like to find out the instances where it happens occasionally

yeah that's a separate problem that I've run into, especially when mixing frontend and backend events, but not at play here