Issues with Scheduled Tasks Using Data Interoperability 3.4 in ArcGIS Pro

[AndrewPadilla]

Hello, Geonet community, @BruceHarold @RenatoSalvaleon !

I'm encountering an issue with ArcGIS Pro 3.4 and Data Interoperability 3.4 when running scheduled tasks created through Pro. Here's the scenario:

1. I created a simple Spatial ETL tool that reads a CSV file and writes it to my desktop.
2. When I run the tool manually in ArcGIS Pro, it works flawlessly.
3. Running the same tool directly within the Data Interoperability Workbench also works without issues.
4. However, when I add the Spatial ETL tool to Pro as a geoprocessing tool and schedule it as a task, it crashes during execution.

I even simplified the workflow to test further, but the issue persists. It seems to be specifically related to running the tool as a scheduled task rather than manually.

Has anyone else experienced similar behavior with Data Interoperability 3.4 and scheduled tasks in Pro 3.4? If so, how did you resolve it?

Any insights, suggestions, or potential workarounds would be greatly appreciated.

Thank you!

[BruceHarold · Accepted solution]

Hello Andrew

You have run into a known issue, we will patch it as soon as possible.

There is a workaround.  If you run your tool from the Workbench app, near the top of the translation log you will find a message containing the console command to run fme.exe with your tool path as an argument, plus any other parameters (but see below*).  If you use Windows Task Scheduler to configure a task with the code it will work.

*If any input parameters do not change at run time (which is typical for scheduled tasks) then do not publish the parameter and it can be omitted from the command arguments.

Another option is to publish your tool as a web tool and schedule that, this requires Enterprise 11.4.

See this example:

https://community.esri.com/t5/arcgis-data-interoperability-blog/etl-pattern-scheduling-web-tools/ba-...

Our apologies for the issue.  It will either be patched in Pro 3.4 or fixed in Pro 3.5 - we are working on that.

[AndrewPadilla]

Hi @BruceHarold , 

Thank you for the quick response. I was able to get the work around you described scheduled.  Thanks again!

Cheers,

Andy

[JoeGuziStarkCountyOH]

@BruceHarold 
is there any update about this issue and the technical article that should be out soon? We are running into this problem as well and it would be great if there was a more permanent solution. Thank you for everything and have a delightful day.

Sincerely,

Joe Guzi

[BruceHarold · Accepted solution]

Hello Joe

The ArcGIS Pro 3.4.3 patch, planned for March 18th, subject to testing, fixes this issue.

Pro will update when the patch becomes available.

Regards

[JoeGuziStarkCountyOH · Accepted solution]

Awesome! Thank you! In the meantime we have a band-aid in place.