topic Re: Windows Task Scheduler Error in ArcGIS Data Interoperability Ques.

Windows Task Scheduler Error

AshleyHayes2 — Wed, 06 Dec 2023 19:39:22 GMT

When I run Data Interoperability via Windows Task Scheduler, I receive an "ERROR : Python Exception <ExecuteError>: ERROR 160236: The operation is not supported by this implementation. Failed to execute (DeleteRows)." from my shutdown script.

When I run it manually in ArcPro, I do not receive any errors and everything works as expected.

Any suggestions?

Also, @BruceHarold -- is there a way to subscribe to your "What's New in ArcGIS Data Interoperability" blog posts?

Thank you!!

Re: Windows Task Scheduler Error

BruceHarold — Wed, 06 Dec 2023 19:28:40 GMT

Hello Ashley

It seems you have struck an issue we haven't found a cause for:

https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/160001-170000/tool-errors-and-warnings-160226-160250-160236.htm

If you open a support call the analyst can look at your workflow.

Re. subscribing, if you subscribe to the whole Data Interoperability board you'll get everything, and thank you for asking.

Re: Windows Task Scheduler Error

A_Baker_ — Mon, 22 Jan 2024 23:29:26 GMT

Hi Ashley,

Were you able to resolve this issue? I have been intermittently encountering the same error while running scripts through Task Scheduler and have been unable to determine the cause or a fix.

Thank you!

Re: Windows Task Scheduler Error

xanderm — Mon, 13 May 2024 12:05:59 GMT

Any luck?

Re: Windows Task Scheduler Error

GB_-_JonathanJew__GISS_ — Thu, 14 Aug 2025 18:05:27 GMT

This is still a problem. I had a bat script running for a little over a month with no issues. Now it consistently fails when run from scheduler, no issues at all from manually running the bat. The only thing that coincided with the crash was logging back into my AGOL portal. the script seems to still be able to read and recognize it is in the correct portal.

I get the same error using deleteFeatures() and/or DeleteRows()

Re: Windows Task Scheduler Error

BruceHarold — Thu, 14 Aug 2025 19:04:49 GMT

I think you should open a support call, it will be hard to troubleshoot here.

Re: Windows Task Scheduler Error

D_Atkins — Thu, 14 Aug 2025 19:11:42 GMT

Just chiming in that we have had the same experience as Jonathan. Python script randomly fails at .DeleteRows with error 160236 (which is why I subscribed to this discussion).

The 'schedule' is monthly, so running the script manually is acceptable (for this case, for now). We've tried different user accounts, administrative user accounts, 'run with highest privileges', and more.

Re: Windows Task Scheduler Error

BruceHarold — Thu, 14 Aug 2025 19:32:30 GMT

OK, sorry to hear that but the good news is the team at Esri will act on reproducible issues so sharing your code will help with that.

Re: Windows Task Scheduler Error

GB_-_JonathanJew__GISS_ — Fri, 15 Aug 2025 16:41:49 GMT

my account does not have support ticket enabled. I've included the directory and aprx with a readme of how it is being used if that is helpful. Generally, it is a very simple and just republishes a subset of features from one feature service to another.

Re: Windows Task Scheduler Error

D_Atkins — Tue, 26 Aug 2025 16:15:22 GMT

Like Jonathan, my account is not an "authorized caller", so I won't be able to escalate this beyond the Community.

Re: Windows Task Scheduler Error

GB_-_JonathanJew__GISS_ — Tue, 26 Aug 2025 18:12:20 GMT

I don't consider this a true solution, but in case it helps folks:

The feature class that was causing issues in my case was a hosted feature service.

Rather than using arcpy's deleteFeatures() and deleteRows(), I was able to accomplish the same effect by using the arcgis API instead.

gis = GIS("home") # Uses active Pro sign-in

fl = gis.content.get("<your feature ID>").layers[0]

fl.delete_features(where="1=1") # Deletes all features

Obviously, this would only work for hosted features classes.

In my case, spatial queries were disabled on the server, forcing me to do spatial analysis locally with arcpy, so the resulting code is a mishmash of arcpy and arcgis for python, but it works within task scheduler.

Re: Windows Task Scheduler Error

BruceHarold — Tue, 26 Aug 2025 18:33:18 GMT

I haven't tried it but I think you can abstract working with any type of feature layer in core ArcPy and delete any or all features as you see in the examples here:

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/delete-features.htm

Re: Windows Task Scheduler Error

GB_-_JonathanJew__GISS_ — Tue, 26 Aug 2025 21:50:23 GMT

Yes, but it is precisely that function that causes the error in question. My workaround is explicitly avoiding that function because it causes the:
ERROR 160236: The operation is not supported by this implementation.

Re: Windows Task Scheduler Error

BruceHarold — Wed, 27 Aug 2025 13:11:37 GMT

OK thanks, the reply chain got lost. I'll see if the tool owner has any insights, not being able to log a support call makes it harder.

Re: Windows Task Scheduler Error

MariaGiarrusso — Wed, 07 Jan 2026 18:46:48 GMT

Having same issue. Using a Pro Model. I call it from a batch file that gets scheduled every night. Worked fine for a while and then it started throwing errors. This post suggested cleaning up temp files as a solution. Worked for some, but did not work for me. Solved: Re: "The operation is not supported by this implem... - Esri Community

Will start a case w/ ESRI.

Re: Windows Task Scheduler Error

MariaGiarrusso — Tue, 13 Jan 2026 19:20:32 GMT

Opened a case w/ ESRI (#04082860). Was able to resolve this issue by verifying that I didn't hit one of the limitations below (which I did - versioned data as an input to append was not supported) AND cleaning out the temp folder C:\Users\<user>\AppData\Local\Temp

Per ESRI, things to check:

Python scripts that contain expressions to truncate and append to hosted layers within ArcGIS Online can often experience issues. There are a few limitations when working with truncates and ArcGIS products. For example:

Truncate on a standalone SQL database table is not supported.
Complex data types such as terrains, topologies, and network datasets are not supported as input.
Versioned data is not supported as input.
The input database table or feature class must be from a database connection established as the data owner.