Differences between scheduled publish and normal publish

Great, thanks for sharing.

Nice article. I didn't realize schedule publishing not fire off event. Do you have any solution make it happen automatically?

Thanks!

I haven´t actually tried to force the publish event when using scheduled publish but I doubt that there is a way. I might be wrong though.

I found this blog post when I had issues with output cache being not cleared after scheduled publish. I was really surprised that lifecycle events are not fired so I did debug and well... those are fired up. DelayedPublishedJob runs `PublishOnBehalfOf` method which calls regular ContentRepository's Publish method which calls all lifecycle events (i.e RaisePostEvents which then fires PublishedEvent). My issue was (and maybe so was yours) that one of my custom event handlers was throwing an exception. Look at `PublishOnBehalfOf` method (Episerver.Util.DelayedPublishJob):

private void PublishOnBehalfOf(ContentReference contentLink, string user)
{
  IPrincipal currentPrincipal = Thread.CurrentPrincipal;
  try
  {
    Thread.CurrentPrincipal = (IPrincipal) new GenericPrincipal((IIdentity) new GenericIdentity(user), (string[]) null);
    this._contentRepository.Publish(contentLink, AccessLevel.NoAccess);
  }
  finally
  {
    Thread.CurrentPrincipal = currentPrincipal;
  }
}

so what happens here is Publish throwing (well, my custom event handler is) and exception. It stops executing other event handlers and it gracefully jumps to finally block with no trace of exception being thrown. (status of Publish Delayed Content Versions is just "Nothing was published." - no error). 

So once I fixed my custom event handler I got all lifecycle events fired up and one of them was probably one responsible for clearing output cache. 

Bottom line is: if status of job is "Nothing was published" when actually it was published than you probably have some issues with you event handlers.

Note: I'm working on EpiServer 10.10.4, I didn't check newer versions