You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2018. It is now read-only.
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:
The text was updated successfully, but these errors were encountered:
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?
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: **[email protected]* <[email protected]>
*@pbearne <http://twitter.com/pbearne> *or +pbearne
<https://plus.google.com/u/0/100456877588970933323>
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:
The text was updated successfully, but these errors were encountered: