Open siparsons opened 7 years ago
I may have found something bit I could do with you checking my logic @pbearne.
After using a refresh token it looks like the old refresh token is expired and a new one provided. However, I am struggling to find the area of the code where we take the new refresh token and store it for future use.
Is it possible that the refresh token only works on the initial attempt?
Appologies if this is way off the mark.
I will dig this out
We have just added pause into the code as part of the fresh token code in-order to help fix this issue
check the latest version of the code on github
I will reply more fully on Monday
Paul
Paul Bearne Freelance Senior Full-Stack WordPress Developer Cell: +1 647 780 7594 Home Office: +1 416 792 8894 *E-mail: *paul@bearne.com pbearne@gmail.com @pbearne http://twitter.com/pbearne or +pbearne https://plus.google.com/u/0/100456877588970933323
On 9 June 2017 at 15:26, siparsons notifications@github.com wrote:
I may have found something bit I could do with you checking my logic @pbearne https://github.com/pbearne.
[image: image] https://user-images.githubusercontent.com/18097657/26991301-bde00be2-4d51-11e7-9881-4752702f6538.png
After using a refresh token it looks like the old refresh token is expired and a new one provided. However, I am struggling to find the area of the code where we take the new refresh token and store it for future use.
Is it possible that the refresh token only works on the initial attempt?
Appologies if this is way off the mark.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pbearne/Bullhorn2WP/issues/15#issuecomment-307478543, or mute the thread https://github.com/notifications/unsubscribe-auth/AAC0virmMyuqJx4sED28ZpTYhItj8Udjks5sCZxhgaJpZM4N1d0A .
I believe there are issues connecting to the bullhorn api, which I first suspected might be due to a timeout which I now suspect are more serious and potentially relate to keeping the auth token alive.
The error we get as part of the CV upload (which our end users are seeing) relates to the code below: