Select to view content in your preferred language

ArcGIS Pro Named User programmatic check out for scheduled tasks

603
4
08-14-2025 04:17 PM
Status: Open
Labels (1)
AdamMesser1
Regular Contributor

Automation workflows on dedicated scheduled task machines running ArcGIS Pro suffer from named user authentication time outs. To avoid the task user being timed out, the current suggestion is to use a dedicated single use license. With the move to named user/user type licensing, we need a method that will allow the task user to re-log in or remain logged in to ArcGIS Pro. Ideally, this would be made possible via a programmatic process that could work with any scripted workflow conducted on the task machine.

Benefits

  • Scheduled task user will remain logged in to the task machine to provide uninterrupted capability
  • Named user user type/ licensing will allow the same licensing model to be applied to all organization users
4 Comments
MichaelVolz

So if you setup an ArcGIS Pro based Scheduled Task to run whether user is logged on or not is there a chance the named user authentication will time out?

SimonSchütte_ct

As workaround you can take the license offline.

If it is a reproducible problem (I have not experienced it myself), I agree that the underlying timeout issue should be addressed, so that workarounds such as Single Use licenses or offline licenses are not necessary.

AdamMesser1

@MichaelVolz - Correct, once a named user logs in, their Pro licensing is active. However, after appx 2 weeks the named user will be timed out/ logged out. At that point Pro is no longer licensed to run any process using Pro resources (e.g. arcpy) and tasks will fail.

@SimonSchütte_ct  - Offline licensing is an option, with a timeout or until license/subscription end dates. In these posts (Taking ArcGIS Pro Offline - Esri Community, Solved: ArcGIS Pro offline license timeout - Esri Community) this is discussed, however both note offline licenses being lost or corrupted (Error: Failed to Return the Offline License.). Experience with lost licenses prompted our use of single use licensing.

Related Posts:

SimonPook1

Having similar issues. Enterprise in in Azure. Servers are set to disconnect users after logging out. ArcGIS Pro is set up to run under a service account, but without repeatedly logging in manually, it will log the service account out after 15 days.
All overnight scripts are set to "Run whether the user is logged in or not" under the service account.
When the log in times out, the tasks still report running successfully, but nothing runs.
Don't have licenses to take offline any more under the new license model, and experience with doing that in the past has shown issues arise after Azure patching/updates are applied, as the Machines ID will change, causing the license to become corrupted or lost.
IM would very much prefer I wasn't logging in with the service account every 15 days to refresh this, but currently there appears to be very few other options.