500 error on all POST requests to `constituent/v1/constituents`
Around the end of June, all of our POST requests to create constituents at `constituent/v1/constituents` suddenly started receiving 500 errors. Not a single one has succeeded since then. Other calls are fine. Queries to constituent API succeed, POSTS to the gifts api succeed. This is the only endpoint, and it's inexplicable. I took a request body from one of the failed requests, and used it to make a request via the API explorer on the dev website, and it succeeded just fine, so it does not appear it has to do with the request body (even if there was a problem with the request body, doggone sure it should not receive 500). The other calls succeeding indicate that the Auth is fine. What gives y'all?
Comments
-
Interestingly enough, if I hit the api with a request_body that triggers an error (like missing phone type), I actually get the proper 400 response with error code. But if I change the phone type back to an acceptable one, leaving all else the same, I get a 500. That makes no sense.
0 -
@Kevin Hathorn
Anytime we are seeing 500 errors we would want to look into those as bugs. For anything bug related we would route you to our support folks to get basic troubleshooting data gathered and they would then send it to the engineering side. I will give them a heads up that this is coming so they don't just refer you back to the community.2 -
@Anthony Gallo
thanks Anthony for the response and heads up. Looking forward to getting this resolved ?0 -
We are experiencing the same bug and found that the post requests for constituents are no longer generating import ID's. Manually adding one allows you to post a constituent again but after one successful post it breaks again due to that constituent not having an import ID. Support referred me to here so hoping this gets resolved soon
1 -
@Anthony Gallo Any developments on this? It looks like things started to work again a few days ago, guess that means the bug was found and fixed?
0 -
@Kevin Hathorn Did you get around to having support file a bug for this? I don't remember my team seeing anything but if that happened it is possible it was routed to another team depending on where the issue was living.
0 -
@Kevin Hathorn it looks like support did get a bug to us and we had 2 fixes put in place so it did not just magically fix itself.
1
Categories
- All Categories
- 6 Blackbaud Community Help
- 213 bbcon®
- 1.4K Blackbaud Altru®
- 403 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 656 Blackbaud Grantmaking™
- 577 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 939 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.6K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 248 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 241 Member Lounge (Just for Fun)
- 34 Blackbaud Community Challenges
- 37 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Grid View Batch
- 3 (Closed) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 794 Community News
- 2.9K Jobs Board
- 54 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)