When using the ArcGIS Online Feature Writer, sometimes during truncation, AGOL will encounter an error on delete. It looks like this:
2022-01-12 18:39:01| 25.9| 0.0|INFORM|ArcGIS Online Feature Service Writer: Truncating layer/table 'Meters'. 2578 features remaining
2022-01-12 18:39:39| 26.1| 0.2|INFORM|ArcGIS Online Feature Service Writer: Truncating layer/table 'Meters'. 1578 features remaining
2022-01-12 18:40:47| 26.2| 0.1|WARN |ArcGIS Online Feature Service Writer: 'deleteResults' error for a feature in 'Meters'. The error code from the server was '1018' and the message was: 'The specified feature could not be deleted or does not exist.'
2022-01-12 18:40:47| 26.2| 0.0|WARN |... Last line repeated 315 times ...
2022-01-12 18:40:47| 26.2| 0.0|ERROR |ArcGIS Online Feature Service Writer: 6000 features successfully deleted from layer/table 'Meters', but the server rejected the 1000 deletions in the last request due to errors. See warnings above. Aborting translation
2022-01-12 18:40:47| 26.2| 0.0|ERROR |ARCGISONLINEFEATURES writer: A fatal error has occurred. Check the logfile above for detailsFor some unknown reason, some features take offense to being deleted. I have tried to determine which features are causing the problem, but at this point, I have been unable to do so.
The strange part is that, if I rerun the writer to continue the truncation process, it picks right back up where it left off and continues to truncate the table. Often there will be yet another feature that has an issue being deleted, and it the writer will encounter an error and stop again. Eventually, after maybe 2-6 restarts of the writer, the table will eventually be truncated fully, and the new features will be written, so far, without incident.
My questions is, is it possible to have the work bench automatically run the feature writer multiple times if it encounters an error? Instead of terminating the work bench, I would prefer it try to write over and over again, maybe 10 times.
Alternatively, if anyone knows how to identify which individual features are causing the issue, I may be able to address the problem that way. I would assume that I need to change the number of records to commit to just one (1), though I am not sure how to have FME give me feedback from something completely contained to the one writer.