title: Service Fabric Reminders
body: <p><a href="https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-actors-timers-reminders#actor-reminders" rel="nofollow noreferrer">Documentation</a> says:</p>
  
  <blockquote>
    <p>Reminders are a mechanism to trigger persistent callbacks on an actor at specified times. Their functionality is similar to timers. But unlike timers, reminders are triggered under all circumstances until the actor explicitly unregisters them or the actor is explicitly deleted. Specifically, reminders are triggered across actor deactivations and failovers because the Actors runtime persists information about the actor's reminders.</p>
  </blockquote>
  
  <p>Let's say we have a reminder set to run after 1h, but the Actor has an idle timeout of 10 minutes and scan interval of, say 2 minutes (set in the actor's <code>ActorGarbageCollectionSettings</code>).</p>
  
  <p>What happens after the first 15 minutes the Actor is idle so is GC'd and deactivated.. so how does it know to recreate the actor 45minutes later? And how does it know what actor ID to use to create the Actor with?</p>
  
  <p>Asking becasue I am wondering how these patterns work:</p>
  
  <p><a href="https://www.codit.eu/blog/2016/08/25/how-to-enable-automatic-scheduling-in-service-fabric-actors/" rel="nofollow noreferrer">https://www.codit.eu/blog/2016/08/25/how-to-enable-automatic-scheduling-in-service-fabric-actors/</a></p>
  
  <p><a href="https://dajbych.net/azure-service-fabric-scheduled-tasks" rel="nofollow noreferrer">https://dajbych.net/azure-service-fabric-scheduled-tasks</a></p>