How Can I Resolve Access Issues Between My PipeDream and Jobber Accounts?

Which setting do you have for refresh tokens on the Jobber side?

I enabled the refresh token feature in the Jobbed Dev Account, but during testing yesterday, I encountered an issue where after some time, PipeDream side returned an error indicating an invalid token when attempting to call certain GraphQL queries.

Would it be possible to test without that setting on instead?

Absolutely, I’ll give a try and let you know if the problem with disconnecting is still happening.

I’m worried that it’s still keeping disconnecting. After some time of testing I got 401 from Axios Access token expired

Can you confirm that you’ve turned off refresh token rotation on your app?

And can you reconnect for now - I will monitor the logs to see what I can find as well. With refresh token rotation turned off, there should not be a 401 error with the refresh token request, as it should be a long lived token.

Confirmed, refresh token rotation is turned off on my end.

Reconnected :wink:

So far so good. I didn’t experienced any disconnection after yesterday’s reconnection.

same with my app that i created for testing. I think it may have taken a cycle to clear out the old refresh settings…?

everything is looking good on my end - i’ll continue to monitor and we can check back in on Monday here.

Quick update, just got disconnected from Jobber Dev Account a few minutes ago, so maybe you can find something useful in the log.

AxiosError - Request failed with status code 401
{"message":"Access token expired"} 
    at null.settle (/pipedream/dist/code/3c66e0556d961d1898f6463ce845046e24eb6dc79e0ba301bf939262c823d348/node_modules/.pnpm/axios@1.6.8/node_modules/axios/dist/node/axios.cjs:1966:12)
    at Unzip.handleStreamEnd (/pipedream/dist/code/3c66e0556d961d1898f6463ce845046e24eb6dc79e0ba301bf939262c823d348/node_modules/.pnpm/axios@1.6.8/node_modules/axios/dist/node/axios.cjs:3065:11)
    at Unzip.emit (node:events:530:35)
    at null.endReadableNT (node:internal/streams/readable:1696:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at null.callAxios (/pipedream/dist/code/3c66e0556d961d1898f6463ce845046e24eb6dc79e0ba301bf939262c823d348/node_modules/.pnpm/@pipedream+platform@1.6.0/node_modules/@pipedream/platform/dist/axios.js:110:26)
    at (file:///pipedream/dist/code/3c66e0556d961d1898f6463ce845046e24eb6dc79e0ba301bf939262c823d348/component.mjs:43:27)
    at null.executeComponent (/var/task/launch_worker.js:287:22)
    at MessagePort.messageHandler (/var/task/launch_worker.js:786:28)

Looking into this today Jakub

, I just want to rule something out - are you attempting to connect the Jobber app again when the app disconnects by chance?

Thank you . No problem at all. Once it’s deployed I can do reconnect.

Sorry, to clarify my question, I’m trying to get to the root cause of why the app is getting disconnected, as it hasn’t happened again on my side. Are you taking any action that might cause it to disconnect, e.g., creating a new connection for the app while one is already made?

No, not at all. Yesterday, I reconnected the Jobber Developer Account and deployed a test workflow to carry out some subsequent steps. However, today I encountered a very peculiar situation. Despite the account being properly connected in the accounts tab, the workflow associated with it failed again, due to an expired access token.