Hi,

Can you check if the autonomous update that you run through FME server also gives the same error if you download the workspace and run it from FME Workbench? The usually makes it easier to troubleshoot for yourself as well. Unfortunately I don't really know what causes the error as you have already double checked your input data and your feature service attributes. An option for troubleshooting might be to try and add a feature with no attribute data to see if that does works. 

But mostly I would try and avoid the ArcGIS Online Feature Service Writer and use a HTTPCaller and construct the call yourself. You usually need to also use Postman to look how an applyEdits call looks like and then you can rebuild it in FME. This way you generally have way more control over what is being sent to the ArcGIS server. Unfortunately it is also more technical and not as user-friendly. Here you have some documentation on the apply edits ArcGIS rest command:https://developers.arcgis.com/rest/services-reference/enterprise/apply-edits-feature-service-layer/

Hello Birgit.

Even using the workspace on FME Workbench, I had the same problem. On the other hand, I validated my FeatureWriter and we found some errors, raised by a colleague who looked at my Workspace:

• The Attribute Definition must be in manual mode and not in automatic mode to proceed without writing issues;

• 

• Certain fields containing area values ​​had an integer and decimal part separator with a comma and others with a dot, probably generated by a different separator configuration from a user who had configured their Windows to have a separator with period rather than comma while the default configuration is a comma. Often a problem encountered when installing the French version of Windows.To get around the problem, we published the area of ​​the geometry (ShapeArea) rather than that entered in the database manually by users.

The validation of the Workspace in FME Worbench (Form) was positive.

Once pushed to FME Server (Flow), I encountered another problem but this was quickly resolved. This was a limitation of ESRI licensing accessibility by too many simultaneous users compared to the number of licenses available. FME Server which requires one did not have one available at the time of testing. Subsequently, the recurrence tests began positive when choosing a recurrence period outside of normal user presence hours.

Consider my case settled and thanks for the comments! I will validate the possibility of substituting the FeatureWriter into a HTTPCaller/Postman.