some tasks failed. see the tasks screen for more info.

And then it continues to run fine at its scheduled time, for days or weeks at a time, only to eventually fail, seemingly out of the blue. net console app and everything finishes without anomaly. And here's the strangest part to us: If I manually kick off the scheduled task, it runs fine, it invokes the. There are no errors recorded in the event log or in the scheduled task interface itself. Once a Query object is created, you can set its properties to conform to the filtering requirements. Query is used to define parameters to filter a layer's features, either by its attributes or its geometry. The tasks which stopped running do not run again on their own, despite being indicated as scheduled to run every night. Requirements: ArcGIS Online hosted feature service (s) or ArcGIS Server service (s) 10.1 or greater. When they stop running, the scheduled task interface correctly shows their last run date, which is a day or more behind the other tasks, which have continued to run at the scheduled time. Two of the tasks seem to sporadically stop running from time to time, and it's currently a mystery as to why. Each task invokes a separate copy of the app, each copy having a different lookup ID value in its config file.Īll but two of these tasks run reliably every night. net console app that pulls data from a SQL db and posts it to a web service. net app, I've got about 20 scheduled tasks set up on a server, all of which basically do the same thing: invoke a small. The time to task failure was longer for the force tasks (576 80 and 325 70 s) than for the position tasks (299 77 and 168 35 s) at target forces of.

Some tasks failed. see the tasks screen for more info.