<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Error Handling service timeouts in ArcGIS JavaScript Maps SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/error-handling-service-timeouts/m-p/502996#M46712</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Am I seeing this correctly?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've begun using the onError event with my services to indicate to the user that there's an issue when my application loads. This works great when it throws something like a 500 error, etc. Recently, we had a situation where the services were just reaching the 60 second timeout limit. When I was trying to debug this, I noticed that the onError event was called at the conclusion of the 60 second timeout but that the error variable (i.e. layer.on("error", function(error){...})&amp;nbsp; ) is undefined when the "error" is a service timeout.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this as designed? Should I or should I not assume that an undefined error variable within that function is a service timeout?? In other words, is it likely that other "errors" may trigger the onError event but leave the error variable as undefined?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Jan 2015 16:37:28 GMT</pubDate>
    <dc:creator>SteveCole</dc:creator>
    <dc:date>2015-01-06T16:37:28Z</dc:date>
    <item>
      <title>Error Handling service timeouts</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/error-handling-service-timeouts/m-p/502996#M46712</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Am I seeing this correctly?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've begun using the onError event with my services to indicate to the user that there's an issue when my application loads. This works great when it throws something like a 500 error, etc. Recently, we had a situation where the services were just reaching the 60 second timeout limit. When I was trying to debug this, I noticed that the onError event was called at the conclusion of the 60 second timeout but that the error variable (i.e. layer.on("error", function(error){...})&amp;nbsp; ) is undefined when the "error" is a service timeout.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this as designed? Should I or should I not assume that an undefined error variable within that function is a service timeout?? In other words, is it likely that other "errors" may trigger the onError event but leave the error variable as undefined?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jan 2015 16:37:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/error-handling-service-timeouts/m-p/502996#M46712</guid>
      <dc:creator>SteveCole</dc:creator>
      <dc:date>2015-01-06T16:37:28Z</dc:date>
    </item>
  </channel>
</rss>

