Skip to main content


Connector Improvement: Fix Erroneous Aggregation in Zendesk Connector for SLA Applications


Please sign in to leave a comment.


1 comment

  • Official comment
    Ray User

    Hi James,

    Thanks for pointing this out. I believe our implementation works under the assumption that an SLA policy would only ever be applied once to a given ticket. In the scenario it happens multiple times, you're right that we'll discard the older events because our table definition assumes we're merely updating a prior record rather than logging a new event. We'll look into solving this so that all sla policy applications can be tracked individually.