scheduled publish is not working after hours

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Mike LaFleur 5 posts 75 karma points

Mar 22, 2022 @ 16:00

I have received some bug reports stating that documents which are scheduled to publish after hours (3am, as an example) are not publishing until a user logs into Umbraco.

There appears to be a gap in the logs for a few hours, which happens to coincide with the time frame the document should have published (these logs are in UTC, my timezone is EST).

It looks like the application shut down and rebooted itself, and then stopped logging anything until someone logged in on the front end (I am new to umbraco).

Is this failure to publish related to the web.routing umbracoApplicationUrl? (the setting is currently blank in our configs)

{"@t":"2022-03-21T06:08:37.5662744Z","@mt":"{EndMessage} ({Duration}ms) [Timing {TimingId}]","EndMessage":"Booted.","Duration":7669,"TimingId":"f655087","SourceContext":"Umbraco.Core.Runtime.CoreRuntime","ProcessId":13832,"ProcessName":"w3wp","ThreadId":1,"AppDomainId":{num},"AppDomainAppId":"{appId}","MachineName":"{machineName}","Log4NetLevel":"INFO ","HttpRequestNumber":1,"HttpRequestId":"09b9b102-7261-43c5-bbf9-a7a819510e88"}
{"@t":"2022-03-21T10:50:48.4822259Z","@mt":"New url {Url} detected, re-discovering application url.","Url":"{domain}/umbraco","SourceContext":"Umbraco.Core.Sync.ApplicationUrlHelper","ProcessId":13832,"ProcessName":"w3wp","ThreadId":25,"AppDomainId":{num},"AppDomainAppId":"{appDomainId}","MachineName":"{machineName}","Log4NetLevel":"INFO ","HttpRequestNumber":2,"HttpRequestId":"48cbd0b4-82e8-44e3-9073-7787e1bd575f"}
{"@t":"2022-03-21T10:50:48.4822259Z","@mt":"ApplicationUrl: {UmbracoAppUrl} (UmbracoModule request)","UmbracoAppUrl":"{domain}/umbraco","SourceContext":"Umbraco.Core.Sync.ApplicationUrlHelper","ProcessId":13832,"ProcessName":"w3wp","ThreadId":25,"AppDomainId":2,"AppDomainAppId":"LMW3SVC289ROOT","MachineName":"{machineName}","Log4NetLevel":"INFO ","HttpRequestNumber":2,"HttpRequestId":"48cbd0b4-82e8-44e3-9073-7787e1bd575f"}
{"@t":"2022-03-21T10:51:07.3110213Z","@mt":"[{EventType}] Event Id: {EventId}, State: {State}","@l":"Error","@x":"SCM.SharedControls.Interfaces.Exceptions.ScmSsoException: invalid_grant\r\n   at SCM.Composer.Web.Services.IdentityServerCommunicationService.HandleTokenResponseErrors(TokenResponse result)\r\n   at SCM.Composer.Web.Services.IdentityServerCommunicationService.MakeAccessTokenRequestAsync(String code, String redirectUri)\r\n

Copy Link

Ambert van Unen 175 posts 819 karma points c-trib

Mar 24, 2022 @ 19:42

0

Are you perhaps running it on Azure and have 'keep alive' disabled?

Not entirely sure but it could be that with no users the site 'shuts down' to preserve resources, and boots back up once people start visiting again.

Copy Link

Mike LaFleur 5 posts 75 karma points

Mar 24, 2022 @ 19:50

It is being run in Azure. And our applications are recycled every 24 hours (ish).

I have been able to reproduce my problem by scheduling a document and then manually restarting the application.

I have attempted to set the umbracoApplicationUrl in the config (manually on the server) and saw that the log files did not update until I manually hit the application's front end. At that point the following two messages were detected

{"@t":"2022-03-24T19:34:32.8728444Z","@mt":"New url {Url} detected, re-discovering application url.","Url":"{domain}/umbraco","SourceContext":"Umbraco.Core.Sync.ApplicationUrlHelper","ProcessId":11896,"ProcessName":"w3wp","ThreadId":10,"AppDomainId":{num},"AppDomainAppId":"{id}","MachineName":"{name}","Log4NetLevel":"INFO ","HttpRequestNumber":2,"HttpRequestId":"84e671ba-a9fe-4250-a64e-4eecc39fee0d"}
{"@t":"2022-03-24T19:34:32.8728444Z","@mt":"ApplicationUrl: {UmbracoAppUrl} (using web.routing/@umbracoApplicationUrl)","UmbracoAppUrl":"{domain}/umbraco","SourceContext":"Umbraco.Core.Sync.ApplicationUrlHelper","ProcessId":11896,"ProcessName":"w3wp","ThreadId":10,"AppDomainId":{num},"AppDomainAppId":"{id}","MachineName":"{num}","Log4NetLevel":"INFO ","HttpRequestNumber":2,"HttpRequestId":"84e671ba-a9fe-4250-a64e-4eecc39fee0d"}

Copy Link

Mike LaFleur 5 posts 75 karma points

Mar 24, 2022 @ 19:56

0

Is it a requirement that the front end application be hit once, to start the Scheduler?

Copy Link
Mike LaFleur 5 posts 75 karma points

Mar 30, 2022 @ 15:08

0

I set , but my application immediately started getting infinite redirects.

Copy Link
Mike LaFleur 5 posts 75 karma points

Apr 08, 2022 @ 18:23

0

FWIW. I did not find an easy answer to my problem. I ended up reworking the events that we subscribed to, so that our system "published" the content in the future.

Copy Link
is working on a reply...

Please Sign in or register to post replies