Handle deletion of an object which has fields in many microservices of a stitched gateway

[hazem-alabiad]

I am using schema stitching architecture. In my implementation, I have a type that is extended by another microservice. e.g. Organization type is extended by the Website microservice in the following shape:

extend type Organization: @key(fields: "id") { 
  id: ID! 
  websites: [Website!]! 
}

The problem: when deleting an organization we should all associate websites. What is the best practice to do such an action? I tried to publish a message via pubSub implementation of graphql-redis-subscriptions however, seems it is not being executed when the message is published from other microservices.