Unexpected error code 1

Home › Forums › General Issues › Unexpected error code 1

This topic contains 6 replies, has 2 voices, and was last updated by  Zach Shefska 12 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • November 30, 2017 at 1:14 pm #2486

    Zach Shefska
    Participant

    Hi there. Zach Shefska here from Fundraising Report Card.

    This week we ran into an issue with an API integration between our two systems.

    Relevant debug information from our systems:

    Nov 29 07:37:20 frc-Production-backend-i-0616550b240a20007 multiprocessor.log: api.errors.NeonAPIError: Error code(s) 1 occurred while contacting the API: (Unexpected System error occured.)
    Nov 29 07:37:21 frc-Production-backend-i-0616550b240a20007 syslog: Nov 29 12:37:21 ip-16-0-0-73 dhclient[1015]: bound to 16.0.0.73 — renewal in 1415 seconds.
    Nov 29 07:37:30 frc-Production-backend-i-0616550b240a20007 multiprocessor.log: 2017-11-29 12:37:30,763 urllib3.connectionpool:395 24525/Thread-1 DEBUG: https://api.neoncrm.com:443 “GET /neonws/services/api/donation/listDonations?responseType=json&page.pageSize=200&outputfields.idnamepair.id=&outputfields.idnamepair.name=Account+ID&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Date&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Amount&userSessionId=557fedd307535c72ef6e1841a4e8da14 HTTP/1.1” 200 183

    You can see above in bold that the Neon API returned error code 1. Which, from the docs suggests either an issue with Neon’s API or an issue with our API call. Our API call structure has been the same for months, so I do not think it is that.

    Any guidance here would be helpful. Thank you.

    December 5, 2017 at 1:49 pm #2490

    jasoncocking
    Moderator

    Hi Zach,

    Can you tell me if you are including any search criteria in your listDonations request? If so, what was the search criteria in this case?

    If the listDonations request does not have any search criteria, then an error will occur.

    December 6, 2017 at 10:21 am #2492

    Zach Shefska
    Participant

    Hey there, Jason.

    Here’s a bit more output from our system that shows we filter the columns:

    2017-11-29 12:37:20,634 api.integrations:95 24525/Thread-1 WARNING: Retrying unsuccessful api call (1/2): Error code(s) 1 occurred while contacting the API: (Unexpected System error occured.)
2017-11-29 12:37:20,656 urllib3.connectionpool:395 24525/Thread-1 DEBUG: https://api.neoncrm.com:443 "GET /neonws/services/api/donation/listDonations?responseType=json&page.pageSize=200&outputfields.idnamep
air.id=&outputfields.idnamepair.name=Account+ID&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Date&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Amount&userSessionId=
557fedd307535c72ef6e1841a4e8da14 HTTP/1.1" 200 183
2017-11-29 12:37:20,657 api.integrations:95 24525/Thread-1 WARNING: Retrying unsuccessful api call (2/2): Error code(s) 1 occurred while contacting the API: (Unexpected System error occured.)
2017-11-29 12:37:20,719 urllib3.connectionpool:395 24525/Thread-1 DEBUG: https://api.neoncrm.com:443 "GET /neonws/services/api/donation/listDonations?responseType=json&page.pageSize=200&outputfields.idnamep
air.id=&outputfields.idnamepair.name=Account+ID&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Date&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Amount&userSessionId=
557fedd307535c72ef6e1841a4e8da14 HTTP/1.1" 200 183

    This is the request we make:

    GET /neonws/services/api/donation/listDonations?responseType=json&page.pageSize=200&outputfields.idnamep
air.id=&outputfields.idnamepair.name=Account+ID&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Date&outputfields.idnamepair.id=&outputfields.idnamepair.name=Donation+Amount&userSessionId=
557fedd307535c72ef6e1841a4e8da14

    Please let me know what other information I can share. The client is happy to reproduce the error if you want to coordinate a time to monitor the error on your end. Let me know.

    December 6, 2017 at 1:13 pm #2493

    jasoncocking
    Moderator

    Hi Zach,

    Thank you very much for this additional information. I confirmed with one of our developers that the issue with this request is that there are no search parameters in the request that you have provided.

    If you add a search parameter to this request, then you will be able to use this request successfully.

    December 6, 2017 at 1:46 pm #2494

    Zach Shefska
    Participant

    Hi Jason,

    That’s a bit surprising considering this exact same request structure is working for dozens of other Fundraising Report Card and Neon users, but I’ll take this information back to our team and see what they have to say.

    Can you share an example of a search criteria (or link me to the docs)?

    Thanks.

    December 13, 2017 at 8:20 am #2509

    jasoncocking
    Moderator

    Hi Zach,

    Sorry for the delay in a response. We had our development team take a deeper look into this reported issue, and they made a fix.

    You can now run the listDonations API request without search criteria. If you run your previous request, you should now get results instead of an error.

    Sorry for any trouble caused by this issue. Let me know if you have any questions.

    December 13, 2017 at 8:44 am #2510

    Zach Shefska
    Participant

    Jason,

    Thanks for following up. I noticed the other day the user successfully synced their data. Thanks for the speedy work on your end!

    Zach

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.