-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using restforce Oauth login, got Invalid Session Id #33
Comments
Is the token Valid? does the account allow Bulk API ? |
the token seems to be valid, If I query using |
Took a look around and can't see any limitations, the account is from an administrator on a dev org. |
Let me check it out other collaborators work on sale force actively hence they can also help
|
I get the same issue. With Restforce, the authentication middleware seems to automatically handle stale OAUTH tokens, but the salesforce_bulk_api connection fails to create a bulk job with an invalid session id. If I reset the user's session, forcing them to login to Salesforce Oauth again, then the bulk job creation works fine. |
I don't have an active salesforce account so need to look into it. Any more On Wed, Dec 10, 2014 at 11:57 AM, Merul Patel [email protected]
Yats |
DK if helps but here is my code:
|
@bfagundez - potentially related, performing any query with the Restforce client before using it to create the bulk_api client results in a successful bulk run for me. Without the initial query, no good. The Restforce client doesn't seem to hold a session_id until it does something (i.e. a query). Example - this works in my job: |
@lgrig thanks for that hint, it does work well if a query is issued before instantiating the bulk api. |
@lgrig @bfagundez Let me try to work on this for the next version. If anyone has a PR for this do send it |
I had this issue as well, did a few changes so that the requests are done through the restforce client, not through http: cvengros@63b866a |
this is the response when a bulk job is submitted:
Restforce methods work, so login procedure may be ok.
The text was updated successfully, but these errors were encountered: