Bulk API: using Workbench InvalidSessionId (Unable to find session id)

Question

I'm following this (Bulk Api) Trailhead, I have valid SessionId and when I try to authenticate I'm getting the following error:

I have created few records using the same SessionId and I know its a valid SessionId and I'm not sure what else is the issue here.

Error:

> exceptionCode: InvalidSessionId  
> exceptionMessage: Unable to find session id

Workbench:

It sounds like you may have gotten logged out of your Org while in Workbench. Otherwise, once you have a jobId, you can use the same jobId to add as many batches to it as you want but the url needs to be at /services/async/apiversion/job/jobId/batch. You can also query the status of the job or close the job if you have the jobid. — crmprogdev, Commented Feb 16, 2017 at 15:00
I'm experiencing the same issue in Workbench. I haven't logged out of my org, but I still receive the same error message about the session ID. I attempted to log all the way out, and log in again, but to no avail. I even used 3 different browsers, but no luck. — Marypearl Parnell, Commented Mar 17, 2017 at 16:08
Did this error resolved? I do get this error even after trying the way @suresh mentioned — SfdcBat, Commented Jul 26, 2017 at 22:54
I'm not sure what I did but after couple of days I able to complete the trailhead, I'm thinking maybe you need to clear your cache and restart your computer and try? — Nick, Commented Jul 27, 2017 at 15:24
one thing worth noting is that the URL actually needs to be 37 instead of v37... It's different from the services/data/ versioning for some reason — NSjonas, Commented Dec 2, 2017 at 0:11

Suresh Kandru · Accepted Answer · 2017-05-03 00:07:03Z

2

Session id should be in same row in workbench request headers. Please make sure login to developer session and try with this

X-SFDC-Session:00D36000000qbjo!ARoAQKiXWkLN9KMUcrhH8J11saoMuhArYs8JiYpo.WmGWCmPCNrDFS8riEl08mXy.mwC5XgexaZvnRHMSwb27VHIHxjcKSYu

Thanks Suresh

answered May 2, 2017 at 23:59

Suresh Kandru

213 bronze badges

Add a comment |

user71468 · Accepted Answer · 2019-08-01 05:24:00Z

0

Instead of passing token, try passing running user sessionId in 'X-SFDC-Session'. It worked for me.

System.debug(UserInfo.getOrganizationId().substring(0, 15) + '***' + UserInfo.getSessionId().substring(15));

your sessionId is after the *** just to differentiate from OrgId to sessionId

answered Aug 1, 2019 at 5:24

user71468

1

Add a comment |

2 Answers 2