https://community.appian.com/support/w/kb/620/kb-1376-http-query-statuscode-does-not-populate-when-unsuccessfulen-USTelligent Community 12https://community.appian.com/support/w/kb/620/kb-1376-http-query-statuscode-does-not-populate-when-unsuccessfulMon, 23 Jul 2018 03:46:32 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2675e304-3acf-47ef-8c33-ad89aed16955Parmida Borhanihttps://community.appian.com/support/w/kb/620/kb-1376-http-query-statuscode-does-not-populate-when-unsuccessful#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:46:32 AM<br /> <h2>Symptoms</h2> <p>When the HTTP Query Smart Service is run, the status code is stored in the <code>statusCode</code> output variable only if it is a success code (200, 30X). If the query fails, the status code is not saved in the <code>statusCode</code> output variable.&nbsp;</p> <h2>Cause</h2> <p>This issue has been reported to the Appian product team. The reference number for this issue is <strong>AN-66644</strong>.</p> <h2>Action</h2> <p>If a business requirement exists to capture the status code, a workaround is to extract the status code from the <code>errorInfo</code> output variable.&nbsp;</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: June 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, database, application design, open issues</div> https://community.appian.com/support/w/kb/620/kb-1376-http-query-statuscode-does-not-populate-when-unsuccessful/revision/2Fri, 09 Jun 2017 20:46:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2675e304-3acf-47ef-8c33-ad89aed16955Nick Vigilantehttps://community.appian.com/support/w/kb/620/kb-1376-http-query-statuscode-does-not-populate-when-unsuccessful#commentsRevision 2 posted to Appian Knowledge Base by Nick Vigilante on 6/9/2017 8:46:17 PM<br /> <h2>Symptoms</h2> <p>When the HTTP Query Smart Service is run, the status code is stored in the <code>statusCode</code> output variable only if it is a success code (200, 30X). If the query fails, the status code is not saved in the <code>statusCode</code> output variable.&nbsp;</p> <h2>Cause</h2> <p>This issue has been reported to the Appian product team. The reference number for this issue is <strong>AN-66644</strong>.</p> <h2>Action</h2> <p>If a business requirement exists to capture the status code, a workaround is to extract the status code from the <code>errorInfo</code> output variable.&nbsp;</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: June 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, database, open issues</div>