I can confirm that I experienced the same thing with my account. Looking into this further.
I’ve found the root cause of the issue - it relates to there being no expiration being passed back by Jobber, although their documentation states that the access token lasts one hour.
Next steps are scoping out the fix for this, and I’ll follow up with an ETA when we’re able to prioritize this.
Thanks a lot Michael, I really appreciate your cooperation.
Hi , I wanted to provide you with an update. It seems that the disconnection issue is nearly resolved and stable. However, today, after two days, I had to reconnect again. Do you have any updates on your end?
Hi , the fix for this issue is currently in PR review. We should have this fixed by tomorrow, or early next week! Sorry for the inconvenience. For context, we are adding logic internally to deal with the fact that expires_in is not explicitly passed during the oauth flow.
, the fix has been pushed - please let me know if you run into any account disconnections and I can look into it again!
Thank you very much. I’ll continue to monitor the situation, and if I encounter any issues again, I’ll be sure to inform you.
I’m sorry to deliver some unfortunate news, but I encountered another disconnection issue today. It’s becoming increasingly frustrating as I’ve already implemented workflows, and my team depends on them running smoothly. I find myself constantly having to double-check and manually reconnect, which is quite bothersome.
I also wanted to mention that we’re already subscribed to the Advanced plan. Therefore, I would greatly appreciate it if you could resolve this issue with the highest priority. Thank you.
Sorry to hear that Jakub - I’m going to investigate today and I’ll get back to you shortly.
I’ve emailed the Jobber team about this. After testing with a new app that I set up, it looks to me like Jobber is returning the same access token for the access token request, as is returned with the refresh token request (which is unexpected). I’m hoping to get some clarification from their team as this is a nonstandard implementation for OAuth, and want to understand why this is happening and how we can fix this, as it is also not documented in their developer docs.
Thank you, Michael, for advancing this. I understand that the lack of documentation isn’t ideal for our work, but I’m hopeful that we can find a solution soon. This way, other PipeDream users who want to work with Jobber won’t have to deal with these issues either.
Thanks for your patience here as well Jakub and for flagging this - definitely want to make this work as soon as possible.
, can you confirm whether you have seen this issue persist in the past week? I’ve set up some test workflows and have not been able to reproduce the issue. If you’re still seeing it, would you mind sharing the workflow link with me, and enabling access for support?
Since the last time of my manual reconnect on April 3rd, I haven’t experienced any disconnections yet, so it seems the connection is stable. However, if there have been any changes, I am more than willing to provide all the necessary data to support for testing.
Posted thread to Discourse: Why Can't I Access My Jobber Account Through My PipeDream Account?
, I just wanted to check in again, as since the fix was pushed I have not seen my Jobber account disconnect, and was wondering if you have experienced the same.
From my observations over the past few days, everything appears to be stable.
