We’re planning an improvement to how Enterspeed handles Destinations when schemas dynamically change which ones they call. Today, if a Destination stops being included in the Schema, Enterspeed does not automatically send a delete event — which can leave stale data behind in systems like Shopify, Algolia, or other multi‑destination setups.

We see this as an incomplete behaviour, and we’re preparing to align the platform with what most users naturally expect.

What Will Change?

In an upcoming update, Enterspeed will automatically send delete events to Destinations that were previously called but are no longer included the next time the schema runs.

This ensures that external systems stay clean and consistent when the list of Destinations changes based on dynamic source data.

We’d Like Your Input

Before we roll this out, we want to make sure it doesn’t disrupt existing implementations.
If your current setup depends on the existing behavior — where removed Destinations do not receive delete events — please reach out to us.

We want to understand whether this change would impact your workflows or whether the current behaviour has simply been a limitation you’ve worked around.

Please reach out on your Slack support channel or via support@enterspeed.com with any input or questions.

Status

This change is not yet released.

We’re sharing this early so you can flag any concerns before it becomes the new default behavior.