enqueue actions after updating the result set
Created by: camdencheek
We saw an event come through that apparently triggered on 0 results. This shouldn't happen, but it seems like it could happen when we enqueue actions before updating the results for a trigger job. It's not super clear whether this was what caused it, but it's wrong in any case.