Could you please tell me how to properly set up an interrupt? My module works like this: it takes a news item, runs it through a GPT module to rewrite it, and then a router sends it to different social networks. When I place a break on Instagram, I get an error, but there’s no retry. How should I configure it correctly? Or should there be a single dedicated module for Instagram at the end, with no other modules after it?
I have mine set to retry 20 times with 1 min delay and it has never failed. In recent weeks it was rarely activated at all, and from those times it had max 4 retries before succeeding.
1 Like
I went into url and signed up for membership in the meta developer community you mentioned, but I can’t comment. Please handle the error quickly.
tuve el mismo problema solucione aparentemente de esta manera si le sirve a alguien les dejo la captura, algo importante esta en jpg el modulo de canva no en png. un saludo
For the 10th time in this thread - the picture format doesn’t matter. Converting it only waists credits, you will still get the error.
1 Like
That’s exactly what I did and it’s now working fine 
Hi everyone, I’ve received an update from our dev team.
Based on the impact we were seeing for customers, the team conducted additional investigation and identified an approach that works around the underlying issue. Their testing shows that things should now be working as expected.
Please check on your end and let us know if you’re still experiencing this issue.
Thank you all for the detailed reports and your collaboration 
3 Likes
I am still having an issue. I got the “Only photo or video can be accepted as media type. (9004, OAuthException)“ error 3 times today. I also have tried reauthorizing my connection multiple times today. Anyone else still having issues after the solution was identified?
I can confirm this is working a treat for now, nice thank you!
try the approach by @Portal_oprace.pl it works fine for me now after an age of trying and waiting for updates.
This is my fix: https://www.youtube.com/watch?v=aY8P5MHv1fg
I haven´t have any issue for the last 3-4 days. So, I assume the issue has been resolved. No one likes workaround. Thanks!
2 Likes
It looked like it had been fixed, but then had an issue last night? Just checking if anyone else has had the same?
I’m still having the issue ever since the “fix” was deployed…