Salesforce Input Tool - Status 500: Server Error

Hi there

Does anybody know how to fix the following error on the Salesforce Input Tool:

Status 500: Server Error

UNKNOWN_EXCEPTION: An unexpected error occurred.

I get this error when I try to connect to any tables in Salesforce. The Salesforce administrator has confirmed that my login worked correctly and it’s not a problem with my credentials, but I'm not sure if it's a problem with my Alteryx, the Input Tool, or Salesforce. I've tried reinstalling the tool, and using the deprecated version, but still get the error

Last week I was able to connect to all the tables, but one table and would throw the following error on running. I’m not sure if this is related at all?

Error: Salesforce Input (1): Traceback (most recent call last):
File "main.py", line 167, in pi_push_all_records
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\engine\sf_queries.py", line 82, in process_query
loop.run_until_complete(retrieve_query_json(self, query_endpoint, header))
File "C:\Users\[user]\AppData\Local\Alteryx\bin\Miniconda3\lib\asyncio\base_events.py", line 616, in run_until_complete
return future.result()
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\engine\sf_queries.py", line 68, in retrieve_query_json
response = await retrieve_query_json_chunk_parse_response(self, session, endpoint, header)
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\engine\sf_queries.py", line 18, in retrieve_query_json_chunk_parse_response
response = await response.json()
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\Lib\site-packages\aiohttp\client_reqrep.py", line 917, in json
await self.read()
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\Lib\site-packages\aiohttp\client_reqrep.py", line 871, in read
self._body = await self.content.read()
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\Lib\site-packages\aiohttp\streams.py", line 312, in read
block = await self.readany()
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\Lib\site-packages\aiohttp\streams.py", line 328, in readany
await self._wait('readany')
File "C:\Users\[user]\AppData\Roaming\Alteryx\Tools\SalesforceInput_v4.2.4\Lib\site-packages\aiohttp\streams.py", line 250, in _wait
await waiter
aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed

Thanks very much!

Input

Salesforce

Accepted answers

All comments

gyang3

@laurathompson can you check if there were there any failed logins in your Salesforce login history? It there's a failed login, there might be information regarding the reason. Another option would be to reset your security token and see if that may fix the issue. And if all else fails, I'd suggest submitting a ticket with support here: https://community.alteryx.com/t5/Support/bd-p/SupportPage

Let me know if that helps solve your issue and please mark as solution if so!

laurathompson

Thanks for the suggestions, @gyang3 - unfortunately we're still getting the Status 500 error, so have logged a support ticket

Czar

Hey Laura, i have the same issue, did you find out what was causing the issue?

laurathompson

This problem is fixed now, although frustratingly we never found out what was causing the problem, it just started working again one day. At this point, the error 500 switched to a different error, which we could fix by removing the default 'IsDeleted=False' WHERE clause.

I work in a team split between the US and UK, and the US members never got the error 500, so maybe it was a firewall or VPN issue

PanPP

Hi @laurathompson

The solution to your issue is to remove the default 'IsDeleted=False' WHERE clause.

Please mark this post as a solution if it resolves your issue so other community members can see it.

Tparris

A colleague and I had this same error for a few weeks. There is very little info on rectifying the error but I was able to resolve with a simple password change.

Hope this works for anyone else.

laurathompson

@Tparris as it happens, this error recurred today on a different SF instance to the first time. Changing password and security key worked this time!

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703