Instagram Reel Not Working

[fabqui84]

I appreciate it but this isn't our problem to solve and I have way too many workflows and router steps for different things for me to go in and just change this as you've suggested. They need to fix their product!

Ok I understand! You're right, good luck to you!

 

[andrewstrealtor]

I have discussed this issue with the technical team, and they have also confirmed that the error is from the Instagram API. I would suggest that you re-establish the connection with your Instagram account, as this helped one of our users fix the "OAuthException" error.
View attachment 28170

View attachment 28172

I have calculated there are about 160 tasks I would need to change if I follow your suggestion. This CAN NOT happen and you need to fix the issue.

 

[ArshilAhmad]

You can try establishing the new connection through Settings; this will update the connection across all your workflows at once.

 

[andrewstrealtor]

You can try establishing the new connection through Settings; this will update the connection across all your workflows at once.View attachment 28191

View attachment 28192

I did try that and it didn't work.

 

[ArshilAhmad]

I did try that and it didn't work.

Did connections not get updated?

 

[andrewstrealtor]

I made a video but can't send it to you since it's too large. No that did not work.

 

[andrewstrealtor]

See video here... https://andrewst.transfernow.net/dl/20230705k9rfECGX

 

[ArshilAhmad]

I am afraid I don't have any other solution for your issue.

 

[andrewstrealtor]

Still not fixed.

 

[ArshilAhmad]

As mentioned previously, the issue is generated at Instagram's end, so it's not possible for us to fix this.

As a workaround, you can use our new Auto Retry function, which will help you re-execute failed tasks automatically.
.https://forum.pabbly.com/threads/how-to-enable-auto-re-execution-for-workflows-coming-soon.15088/

 

[andrewstrealtor]

Using the auto re-execute task won't solve this issue. You need to fix the connection issue. How can you say it's been fixed when it isn't fixed? I don't understand how you can market connections that don't work and provide instructions for a fix that doesn't fix the issue. I've tried re-establishing the connection and that didn't solve the issue.