Ignoring spans with wrong end/start fields

Happened to a user: the API was sending a higher "start" field than "end" field on a span.