ClusterSharding.Passivate going to Dead Letters

I am seeing ClusterSharding.Passivate messages going to dead letters after sending to the ActorRef[ShardCommand] passed in my entity:

[2021-07-23 17:21:24,844] e[34mINFO e[0;39m e[36ma.a.EmptyLocalActorRefe[0;39m [akkaDeadLetter] [] - Message [akka.cluster.sharding.typed.scaladsl.ClusterSharding$Passivate] to Actor[akka://migration/system/MassResumptionShardCommandDelegator#238785427] was not delivered. [1] dead letters encountered. If this is not an expected behavior then Actor[akka://migration/system/MassResumptionShardCommandDelegator#238785427] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'. - MDC: {akkaAddress=akka://migration@,, akkaSource=akka://migration/system/MassResumptionShardCommandDelegator, sourceActorSystem=migration, akkaMessageClass=akka.cluster.sharding.typed.scaladsl.ClusterSharding$Passivate, akkaTimestamp=17:21:24.843UTC}
   namespace: here-olp-pipeline-management-sit 

Did I miss a step in setting up my akka cluster? I don’t see log messages (logging at INFO) indicating termination of an actor in the akka cluster system.

For my system, I enable “remember-entities” and I have a stop command configured. I verified I only stop the actor via the stop command.

Any guidance is appreciated - Thanks!