Skip to main content
Question

Optimizing ArcGIS Online Writer to avoid time out error 504

  • June 21, 2019
  • 4 replies
  • 231 views
messagemauri
Contributor
Forum|alt.badge.img+6

Currently using FME 2018 Desktop. I have a workbench using the AGOL Writer to write a large data set to an ArcGIS Online Feature Service layer as follows:

Writer mode: INSERT

Truncate First: Yes

Features per request set to 1000

When executing the workbench, sometimes it works and sometimes it Fails and gives the output time out error 504.

What's the best approach to optimize the AGOL Writer or the workbench to avoid timeout issues with AGOL?

 

Thank you.

 

 

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

lars_de_vries
Forum|alt.badge.img+10

In such cases I do the following:

  1. I reauthenticate the AGOL web connection through Tools > FME options > Web connections > right mouse click on connection and select 'reauthenticate'.
  2. You can set the 'Features per request' lower to e.g. 500.

If it still fails, you might want to use another approach, because it will be hard to trace which features (sets) have been uploaded and which haven't.

I'm such cases you could prepare the sets in different tables or databases. Next you can create a new workspace with a WorkspaceRunner. The WorkspaceRunner can call the original workspace. With the new workspace you make sure every dataset is provided.

In the last scenario you'll have a good control of which sets have been written and which ones haven't. Now it is much easier to retry the ones that have failed.

messagemauri
Contributor
Forum|alt.badge.img+6
  • messagemauriContributor
  • Author
  • Contributor
  • June 21, 2019

In such cases I do the following:

  1. I reauthenticate the AGOL web connection through Tools > FME options > Web connections > right mouse click on connection and select 'reauthenticate'.
  2. You can set the 'Features per request' lower to e.g. 500.

If it still fails, you might want to use another approach, because it will be hard to trace which features (sets) have been uploaded and which haven't.

I'm such cases you could prepare the sets in different tables or databases. Next you can create a new workspace with a WorkspaceRunner. The WorkspaceRunner can call the original workspace. With the new workspace you make sure every dataset is provided.

In the last scenario you'll have a good control of which sets have been written and which ones haven't. Now it is much easier to retry the ones that have failed.

Thank you @lars_de_vries! Will give it a shot.

runneals
Supporter
Forum|alt.badge.img+29
  • runnealsSupporter
  • Supporter
  • June 21, 2019

It's a known issue. Believed to be caused by Amazon Cloudfront caching. Working with esri support and development to resolve. Follow this thread for updates: https://knowledge.safe.com/questions/84687/arcgis-online-readerwriter-error-code-503.html

messagemauri
Contributor
Forum|alt.badge.img+6
  • messagemauriContributor
  • Author
  • Contributor
  • June 21, 2019

It's a known issue. Believed to be caused by Amazon Cloudfront caching. Working with esri support and development to resolve. Follow this thread for updates: https://knowledge.safe.com/questions/84687/arcgis-online-readerwriter-error-code-503.html

Thanks for the update link

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.