Urgent - LeadConnector v2 stopped working

[John Michael]

"statusCode": 401,
"message": "Invalid JWT"
Same issue... I manually re-execute the failed steps, and it works for 24 hours... then fails again. Please escalate

 

[ArshilAhmad]

"statusCode": 401,
"message": "Invalid JWT"
Same issue... I manually re-execute the failed steps, and it works for 24 hours... then fails again. Please escalate

Could you please share the Task History ID, where you encountered this error?

 

[John Michael]

It's happening to a lot of them. Here is the latest" IjU3NjUwNTY4MDYzNDA0M2Q1MjZiNTUzMjUxM2E1MTZiNTQzOTBmMzYi_pc

 

[Preeti Paryani]

Hello @John Michael,

Upon checking the task history you shared, it appears that the failed steps were re-executed. Could you please disable the auto re-execution setting and let us know if the issue persists? Additionally, please share the Task History ID so we can investigate further and assist you more effectively.

 

[John Michael]

Hello @John Michael,

Upon checking the task history you shared, it appears that the failed steps were re-executed. Could you please disable the auto re-execution setting and let us know if the issue persists? Additionally, please share the Task History ID so we can investigate further and assist you more effectively.

No, because I need this to work for my clients. More failed today
IjU3NjUwNTY4MDYzNTA0Mzc1MjY1NTUzMTUxMzY1MTY2NTQzNjBmMzQi_pc

You should be able to check Pabbly internal logs

 

[ArshilAhmad]

The logs change when the workflow is re-executed. If possible, please disable auto re-execution temporarily. You can re-enable it once the error has been captured in your Task History. We need a Task History ID that hasn’t been re-executed in order to accurately diagnose the issue.

 

[John Michael]

IjU3NjUwNTY4MDYzNTA0MzI1MjZhNTUzNDUxMzM1MTZhNTQzNzBmMzIi_pc
JUST FAILED.

 

[John Michael]

I will leave this as a failure for 1 hour before fixing. PLEASE REVIEW LOGS

 

[John Michael]

@ArshilAhmad

 

[ArshilAhmad]

Please allow us some time to look into this concern. We will get back to you with an update soon.

 

[John Michael]

I have to re-execute these failures. Did you look at the logs? @ArshilAhmad

 

[ArshilAhmad]

Yes, we did. You can go ahead and re-execute the failed step. We’ll get back to you as soon as we have an update from the technical team.

 

[ArshilAhmad]

Our technical team has informed us that the issue primarily arises because the old token expires and is regenerated every hour. There can be instances where a request is sent using Token A, but during the process, a new Token B is generated. Since LeadConnector only recognizes the latest token (Token B), any requests made using the old token (Token A) will result in an error.

The workaround for this is auto re-execution of the failed step.