Select to view content in your preferred language

Struggling with a Simple Velocity Feed

129
2
Jump to solution
02-06-2025 07:38 AM
JeffSilberberg
Frequent Contributor

Morning All, 

   I am struggling with what should be a simple Velocity Feed, but refuses to accept data

   The post to the Feed is getting :

< HTTP/1.1 500 Internal Server Error
< Date: Thu, 06 Feb 2025 15:23:27 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 72
< Connection: keep-alive
< x-envoy-upstream-service-time: 72
< server: istio-envoy
<
* Connection #0 to host us2-iot.arcgis.com left intact
{"details":"Error id 56c3d099-a3d5-4592-8f55-e4defe2388ca-1","stack":""}

The Feed Logs show no issues what's so ever.  Just an INFO note what I turn on the option.

It's a large JSON object from Weather Stations.  The Object checks clean in a JSON Tool.  What I think the issue may be, but I am not sure how to work around it is that some elements of the Object that messuare thinks like Snow Depth will have a null value if not present, as 0 is a valid Snow Depth if the sensor is present and active.  But the Schema in the Feed is set to a type of float64.  "snowDepthCM":null, "snowDepthIN":null 

So two questions;

  1. How do I get this feed to accept the data and pass it to the RTA.  I need to understand the Error(s) messages I guess.

  2. Which leads to the second issue, how does one debug this? 

 

 

 

 

 

0 Kudos
1 Solution

Accepted Solutions
JeffSilberberg
Frequent Contributor

UPDATE -- 

    Turns out it had to do with a Bad Token being received as a result of the password having Special Characters in it not just alphanumerics.  This even though the Client ID and Password were perfectly valid in the portal.  I don't know if the PHP Curl interface had a problem with the special characters or the documentation is just missing something.  However changing the password fixed the issues being encountered. 

 

Case Closed. 

 

 

 

View solution in original post

0 Kudos
2 Replies
JeffSilberberg
Frequent Contributor

 

Case has been opened -- I will update if I get a resolution.  

JeffSilberberg
Frequent Contributor

UPDATE -- 

    Turns out it had to do with a Bad Token being received as a result of the password having Special Characters in it not just alphanumerics.  This even though the Client ID and Password were perfectly valid in the portal.  I don't know if the PHP Curl interface had a problem with the special characters or the documentation is just missing something.  However changing the password fixed the issues being encountered. 

 

Case Closed. 

 

 

 

0 Kudos