nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcPro 3.0 did not fix scheduled tools

Michael_VanHatten

I am wondering if anyone has been able to get the Tool Scheduler to work with Pro 3.0. There has been a bug ( BUG-000131693.) that has been keeping 2.9.xyz from running scheduled tools. It was claimed by an ESRi employee here https://community.esri.com/t5/arcgis-pro-questions/scheduled-modelbuilder-task-fails-on-select-layer/td-p/1142637 that the issue would be fixed with the 3.o update. I have been waiting weeks for the update, just to find out that I now get a new error message and the scheduled tools do not work. They run without any errors when I manually run them but that is not the workflow I want to use. ESRI claims they were addressing the issue, can anyone confirm that the schedule tools function is working? I am running some very simple model builder tools, nothing fancy, select by attributes and recalculate attributes. No crazy complex analysis, is it just me thinking every time new version come out more problems come up with promises of fixes at the next version?

Find more posts tagged with

Accepted answers

All comments

LMedeirosUI

Hi Drew - I tried a simpler model with just a single calculate field and (to me) it looks like the same thing happens. I've emailed you the DMP files and screenshots for both my original model and the simpler one. Thanks for your help.

model2.jpg

Drew Flater

@LMedeirosUI can you please email me the crash dmp file you are experiencing? You can find it in this folder: C:\Users\<your user name>\AppData\Local\ESRI\ErrorReports with a timestamp matching when the crash occurred. Email to dflater@esri.com.

It would be great if you would contact Esri Support to log the issue with your reproducible steps, so that the development team can work to fix the crash and any problems.

As a workaround, you could try to use different tools, like Calculate Field instead of Convert Temporal Field, which offers Python-based functionality for adjusting or converting temporal field values. I won't know what tool is causing the crash until reviewing the crash dmp file using our development tools.

LMedeirosUI

@DrewFlater I cannot schedule tools to run and am using ArcGIS Pro 3.2.2 running on a Windows 11 virtual machine (via Parallels Desktop 19) as I use a 2023 MacBook Pro (with the silicon processor and Sonoma 14.4).

The model runs fine when run manually, but when I schedule a window pops up that ArcGIS Pro has stopped working (it hasn't - the window can be dismissed and nothing changes in terms of ArcGIS Pro's functionality) and the geoprocessing schedule history remains at (0). I've attached a screenshot of the model's tools. I also submitted the error report to Esri via the pop-up window.

I use a named license through my employer (University of Idaho) and am accessing an AGOL portal outside of my employer.

Any suggestions?

model.jpg

Drew Flater

Hello all, now that Pro 3.2 is available, I wanted to mention that a remaining scheduling bug related to Select Layer By Attribute has been fixed.

https://support.esri.com/en-us/bug/the-scheduled-execution-of-the-select-layer-by-attribut-bug-000159167

I hope that some of those who posted above might be able to upgrade to Pro 3.2 and see if their scheduled tools are working now.

Ramon_de_Leon

I am also having similar issues. I have a model tool (combination of different tools and scripts that I combined in a single ModelBuilder tool) that runs great when ran manually, but every time I run in as a scheduled task or in the "History" panel, I get a bunch of Errors: 000725, 000258 & 000670 (which should not be the case as I have a precondition to delete all feature classes in my workspace before running the parts where I produce the new updated data).

I tried separating deleting the feature classes as a separate tool that runs before running the data update tool but it did not help also. Pretty frustrating to troubleshoot.

XiaoXiao2

I have created a model in Pro 2.8, and it works fine with scheduling in Pro 3.1 and Pro 3.2. It might be an issue specific with your model. Please double check that your project is saved before performing scheduling ( if the project is not saved, there should be a warning when you select scheduling).

Since the issue may be specific, please let tech support to triage your model and they would figure out the issue. Thank you

XiaoXiao2

I see what you mean. Could you please contact esri technical support at 1 (888) 377-4575, so that they can investigate the issue first for you. Thank you

ArmstKP

@XiaoXiao2 I updated Pro to 3.1 today and I still can't run any scheduled models that I had created in 2.8 OR any model I create and schedule in 3.1........

ArmstKP

@XiaoXiao2 I am able to run any model manually, after the update to 3.0. But, any models created in 2.8 that are scheduled will no longer succeed. Even if I create a new model in 3.0 and schedule it, it will not succeed either.

XiaoXiao2

I totally understand that you are having issue with schedule tool. Can you post the issue to esri tech support? Or can you provide me with the repro case with detailed steps?

ArmstKP

@JonathanWhite1 @XiaoXiao2 @Michael_VanHatten After I updated Pro from 2.8 to 3 about two months ago, I am having this exact same issue as well... All 15 of my scheduled models now fail every time. Pretty maddening.

JonathanWhite1

Try deleting the schedule and then saving the model then schedule the model again.

JonathanWhite1

I'm getting the same issues with a similar workflow. Works fine if I run them manually. It appears that Model builder is forgetting file paths and ignoring parameters when set as a scheduled tool. This was the issue in previous versions of pro and still is the issue in 3.0. I have discussed the issue with tech support in great detail and the solution was to wait till 3.0. It doesn't appear to have been resolved. It was working for a bit after 3.0 release but then decided to forget file paths again. Set the file paths as parameters and it worked for a bit but then decided to revert back to forgetting file paths. Been struggling with this problem for well over a year.

XiaoXiao2

Hi @Michael_VanHatten ,

I have created a feature service and feature table to follow your workflow. And created "Add_Join", "Select By Attribute" and "Calculate Field" functions in the model builder. Unfortunately, the issue cannot be reproduced.

In this case, could you please contact esri technical support to take a further troubleshooting process? They will take a look at your data and walk through the steps. If the issue can be reproduced, we will try to fix it for you.

Thanks

Drew Flater

Also @Michael_VanHatten , I forgot to respond to your statements...

1. The error messages you indicate don't have anything to do with data lock. Data lock was the problem I described previously that was responsible for the error I pictured, but doesn't have anything to do with your case(s).

2. The capabilities of the feature services shouldn't impact this case. Yes to run Calculate Field you'll need the Edit capability like you mentioned. But the error messages indicate that the failure is before any calculation is even attempted, when the tool is adding a field to perform a calculation into. This might either be your choice or there is a bug causing the tool to interpret the field you chose as a new field, either due to the data source, the join, and/or both.

Drew Flater

@Michael_VanHatten

Regarding Facility Layer Inspection Update pictured error, this error is coming from the server side when using your data with the AddJoin tool. Can you confirm the model runs from within Pro? Do you have credentials to access those services saved for your account from within Pro? I can imagine a scenario where this error is raised because the external Python process that runs the scheduled model cannot gain access to those services, as it is a headless operation that does not prompt for credentials. When you add those services to a map, or when making a server or portal connection to access those items, make sure the option is checked to Save User/Password or "Sign in automatically" since those are the only ways to make sure the Python process can access secure data sources.

Regarding the other capture.png with Error 000852, this is an error that occurs when you have specified that Calculate Field should add a new field to perform the calculation into, in this case it looks like you have specified as the input field: "L1Facilities_View_2022_Score.condition_rating_2022". Is this intentional that the calculation should be into a new field? Or you got that field by selecting from the input field choice list? There might be a bug happening here with Calculate Field with a joined feature service causing this problem. I will test this scenario while you are responding.

Michael_VanHatten

@DrewFlater I attached the two error messages I get, I have three models I want to run (separately) and I get one of these errors each time I try a scheduled run. I guess I don't understand what this data lock is? I unchecked all the layers and run the tool with ArcPro completely closed on my computer. All the layers in the models are feature services on my enterprise with full abilities to edit attributes and geometry.

Thanks

Capture2.PNG

Capture.PNG

Drew Flater

@Michael_VanHatten the model looks fine.

Scheduled tools support any data format/location, but there are gotchas when working with remote data, covered here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/schedule-geoprocessing-tools.htm#ESRI_SECTION1_ABC4323E12B04D0C90F07B16B3ABE894

If you can screenshot the error messages from the failed task run of your scheduled tool, it will help to know what tool or process is failing and why (like in my failed task that I pictured and described above, you can hover on that and pop-out the messages window to look at the detailed errors/warnings).

Michael_VanHatten

Hi @DrewFlater,

Thanks for the response, I have verified that I am using the correct layers in the tools and have them unopened in the map or project. I would like to run these tools to update a few inspection layers we use to populate dashboards and keep field inspection maps up to date. I noticed that you're using data that is saved in a geodatabase. I am trying to use host feature services from the company Enterprise Portal, is that the issue here?

I attached a screenshot of the model I am trying to run, very simple, adds a join, selects by attributes, calculates a field, removes join.

Thanks

55.PNG

Drew Flater

@Michael_VanHatten while I am not the employee who said in the forum your problem would be fixed in 3.0, I am the one that tested and verified BUG-000131693 is working in Pro 3.0.

Can you please give more details about the errors you are experiencing?

I just retested a scenario like what you described, using a ModelBuilder tool to select some features and calculate a field, run on a schedule. This is completing successfully for me, as long as I do not have the layer/table open in Pro, since that would cause a schema lock with the external scheduled process which is trying to update the data out in Python. You should also double check that if you are using a layer as input to the selection tool, that the project is saved with that layer, otherwise again the external process will not be able to locate what you want to use as input (there are warnings about this in the scheduling UI button, and in the documentation).

So here is what is working for me. I have a dataset, which has 10 or so STATENAME values. I want to select and calculate a field only for those with STATENAME=Wisconsin. So I perform the selection against the data path, then send the result to Calculate Field. The calculation I perform is some basic text, WI, plus a timestamp so I can definitely see that the calculation is being performed at the time that the scheduled process ran.

You can see in the History >Geoprocessing > Scheduled section I have one time that the scheduled process failed. That was for the schema lock that I mentioned before, as I had the data open in Pro, and it could not perform the calculation while the data is locked for use in Pro.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.