Living Atlas Update 2025.1 Content update scheduler did not fire Enterprise Portal 11.4

[DavidColey]

Hello - I tried scheduling the  Living Atlas update 2025.1 for my 11.4 Enterprise Portal.  I went to Organization>Settings>Living Atlas>Schedule update for April 22, 7pm EDT, but nothing happened.

This morning, the Organization>Settings>Living Atlas page still shows me at:

Current content version: 2024.2

Release date: Oct 22, 2024

I know I can update using the 'Update Now' option, but was wondering if there is an admin setting somewhere that prevented the update scheduler from firing.

Thanks,

David

[RobertCollins]

Hi there, 

Sorry to hear the update failed. 

I would review the Portal Admin Logs from the time when the update was intended to run to see if there was noted issue that could have prevented the update running at the scheduled time. 

If you were to trigger the update manually, it might throw an error within the Portal UI and if it does then this might help to explain why the scheduled update didn't occur as you were expecting. 

• One error that I have seen is "unable to reach Living Atlas content updates" which might be because there might be a URL which isn't allowed through that ArcGIS Enterprise needs to reach out to. If this occurs, I'd contact Esri Technical Support for guidance and to verify that the correct URLs are accessible.

It could also be worth exploring whether the REST API can be used for your scheduling workflow. Going through this route require Administrative access and may prevent a role / permission discrepancy (it could be that the update was scheduled using a pseudo admin role as opposed to a full admin).

• /checkForUpdates: Check for Updates | ArcGIS REST APIs | ArcGIS Developers
• /downloadAndInstallUpdates: Download and Install Package | ArcGIS REST APIs | ArcGIS Developers

Hope you get on ok this time around!

[DavidColey]

Hi @RobertCollins - thanks for the reply.  We have Monitor, showing no issues for the portal logs at the scheduled time.  It's possible there was simply a network hiccup on our end as a manual update went fine.  I'd have to start checking event logs.

But for us it doesn't really matter as far as scheduling goes, as I need to update sharing on living atlas layers in our basemap gallery after an update, so a manual update is more suited for our work.