500 error when updating a person

Hello. I’ve been working on pipedrive integration with the api, and it’s been working until today. I’m currently getting an HTTP 500 when doing a PUT with the following

URL: https://api.pipedrive.com/v1/persons/49052?api_token=

JSON body: {
“id”: 49052,
“company_id”: 2334669,
“owner_id”: {
“id”: 13110886,
“name”: “Marketing”,
“email”: “marketing@enterprisepeak.com”,
“has_pic”: 0,
“pic_hash”: null,
“active_flag”: true,
“value”: 13110886
},
“name”: “Aaron Hardin”,
“first_name”: “Aaron”,
“last_name”: “Hardin”,
“open_deals_count”: 0,
“related_open_deals_count”: 0,
“closed_deals_count”: 0,
“related_closed_deals_count”: 0,
“participant_open_deals_count”: 0,
“participant_closed_deals_count”: 0,
“email_messages_count”: 0,
“activities_count”: 1,
“done_activities_count”: 1,
“undone_activities_count”: 0,
“files_count”: 0,
“notes_count”: 0,
“followers_count”: 1,
“won_deals_count”: 0,
“related_won_deals_count”: 0,
“lost_deals_count”: 0,
“related_lost_deals_count”: 0,
“active_flag”: true,
“first_char”: “a”,
“update_time”: “2022-12-13 20:23:04”,
“delete_time”: null,
“add_time”: “2022-12-13 20:23:03”,
“visible_to”: “3”,
“picture_id”: null,
“next_activity_date”: null,
“next_activity_time”: null,
“next_activity_id”: null,
“last_activity_id”: 269308,
“last_activity_date”: “2022-11-21”,
“last_incoming_mail_time”: null,
“last_outgoing_mail_time”: null,
“label”: null,
“org_name”: “Creative Foam Corp”,
“cc_email”: “enterprisepeak@pipedrivemail.com”,
“primary_email”: “ahardin@creativefoam.com”,
“owner_name”: “Marketing”,
“d83386cbd04d064b0b9c2c9ad2214ff712b3d4fe”: “180”,
“6129b40082294a63d5a914caabbab58a2d46448d”: null,
“7a745fdfa9d603ee6dc3f63bb878f2a0f8a1f20a”: null,
“b86956869d3ac8ec38b66a3ff7f2ce239daed99a”: null,
“7bab28d2b952edcaedaa3a6d54bf288d0518d5b9”: “aaronhardin1983@gmail.com (Personal)”,
“3704eacb017c735eeed820d89d0990cbaf59c843”: “https://www.linkedin.com/in/aaronhardin”,
“bbadd995aa0ef6aed1c714f4aea3b0988cfacd3a”: null,
“6ddf5d21b1a3c3cd7ddf73a0bf7a5763bb57537b”: “Director of Information Systems”,
“08c20dcdea0dc5d8782f0b0db9cd9d87d886f27b”: null,
“6bca65174ba9d0ff3d7f559c2092cc4f684d3064”: “88”,
“f84aafeacfdef73ceb1868b8a1ea06413b3c61b2”: null,
“90c3b1422f43aa4adda974d3a9f93aa4d6f42779”: null,
“5d3b6949f2ba426cb9a43004ec0dcb972242651f”: null,
“96d5a0a529005aa99ad84fb6576ce1889058627f”: null,
“f750a3bedaa83d57d4783ab4eb7b047c01228ef5”: null,
“c494a86dbcfeade92c50f691d0a6bed90b9c7a3a”: “197”,
“ee6357ca7849b89b8cffe0ab4d467cc6359bb202”: “198”,
“27046d92bc0c9929ccaded7399193baeb405bee2”: null,
“4ea4b0f7ebaa90242689efe15bda8bdfe564eade”: null,
“13c0295edf21c7b0f51a3a8871681d20272d0970”: 1,
“cc937f8723908aeb3d190b18cbdb902b20bf844f”: null,
“aae19c58bdcacee72bd0503be3ae03314f0250aa”: 0,
“40a12205b137813b0509550418d5d802a4c82d93”: 0,
“c365751ce0f4cd1b74407386af73b80a3293c3ea”: 0,
“be7d332595d39fe2404ed973073c165b189d34d7”: “52”,
“03b44be11d2a2c10bd30fa8566eda4b112a65c20”: “118”,
“7a4d3a839c22799d1c984fe6c790d32b5b4928a3”: null,
“04879c99fc17a8273150a594c49988de94b73f3a”: null,
“a076f05a90cd625a65c537fd1b38b9d466f5a2db”: null,
“36ee217ffb6823a32a66fce130befae0bf4edeff”: “212”,
“b41c7aa1783fba026abdda00a1840f43b7342aad”: “210”,
“a25d54803f0d838c0092a2eab6547da8cf4f68b2”: null,
“556eadcd662756ec8658a701445f6ef0a5bc9bb9”: null,
“organization”: {
“name”: “Creative Foam Corp”,
“people_count”: 1,
“owner_id”: 11327451,
“address”: null,
“active_flag”: true,
“cc_email”: “enterprisepeak@pipedrivemail.com”,
“value”: 32449
},
“email”: [
ahardin@creativefoam.com
],
“phone”: [
{
“value”: “(423) 649-2757”,
“primary”: true,
“label”: “Work”
},
{
“value”: “(810) 629-4149 (HQ)”,
“primary”: false,
“label”: “Other”
},
{
“value”: “(423) 333-2379”,
“primary”: false,
“label”: “Mobile”
}
]
}

I’ve also tried with org_id instead of org, same result.
is anyone else experiencing similar issues?

Hi @Jim
Welcome to the community :wave: and thanks for being patient. Can you share some additional details?

  • What are the fields being updated? Can you list them if possible
  • You mentioned that the failure happened after a particular point in time - is it sporadic, or does it happen every time?

You can see the list of fields detailed in the post body above. Upon further investigation with trial and error, the issue seemed to be with ‘visible_to’. Removing that seems to have fixed the problem for now, and we don’t need to update that field.

Thanks for sharing this detail @Jim. That’s a good catch. Let me try to replicate on my side and follow up