The operation failed with an error. this.imtInternalError.toJSON is not a function.! Eror just because tags and categories
!
Screenshot 2024-12-13 233726|690x401
2 Likes
Iâm getting the exact same error today using the âCreate a Media itemâ module for Wordpress. My scenario worked fine yesterday, made no changes, now it gives this error.
Iâve re-connected my account, made a new scenario, same problem.
Is this a Make.com problem?
3 Likes
Yes, I have experienced the same thing. Everything was working fine until today. If you manage to fix the issue, could you please tell me how you did it?
1 Like
Same problem with the same module. Canât find the fix.
1 Like
Exactly the same problem here. Gets error message in Make´s Wordpress Module.
this.imtInternalError.toJSON is not a function
Appeared suddenly with no changes made. Problem seem to be with their module and tags and category configuration when creating a post. Hopefully they fix soon.
2 Likes
Same issue here. Create a Media Item (WordPress) module is returning error âthis.imtInternalError.toJSON is not a functionâ @Support_Team1
Any update on this error? Iâve been having it for the last 3 days as well with the âwatch for new postâ module for wordpress.
1 Like
Hello everyone @here, thank you for raising this in the community.
The issue should be resolved so all should be up and running now. Could you please test on your end and see if everything is working as expected?
If youâre still experiencing this issue, please open a support ticket with our Care Team, who will help you further investigate this.
Thank you very much for your cooperation and understanding 
1 Like
Nope not fixed still getting this error. I also note that opening a support ticket its not really clear where you go to report the error. You could work on making your support choices clearer.
2 Likes
Hello @contentvault_content, Iâm really sorry to hear that youâre still experiencing this issue.
Here are the steps you can follow to report this in a ticket
- Select Technical challenge from the dropdown
- Based on the behavior described in this thread, it seems that youâre encountering an error in your scenario. Please choose the relevant options from the following dropdowns:
- Pick the specific type of error youâre experiencing. If none of them apply, please select Other.
- Finally, in the description fields that pop up, provide the following details to help us investigate:
- The app involved.
- A description of the error behavior.
- Execution UR.
- Any relevant screenshots for reference.
1 Like
Hello everyone, I have also been receiving the same error since this morning. It affects all WordPress modules in Make
1 Like
Hello everyone @here
It seems the issue has unfortunately returned. Weâve reported this to our dev team, and theyâll be looking into it as soon as possible. Weâre truly sorry for any disruptions and inconvenience this is causing.
Iâll update you in this thread as soon as thereâs any news to share. If youâd prefer to receive updates directly in your inbox, please open a support ticket with our Care Team, and theyâll do the same.
Thank you very much for your patience and understanding.
1 Like
What ever change was made to WordPress module in the last week needs to be reversed.
It comes up with error
But when you go into the module it appears that there is some JSON connection error when it tries to bring in tags and categories.
Hello everyone @here
I wanted to step in and let you know that the issue causing the this.imtInternalError.toJSON is not a function! error has been resolved, and everything should now be working as expected.
Regarding the Function âfixBOMâ finished with error! message, this is not an issue on our end. This error occurs due to an incorrectly created connection, where the API response returns HTML code instead of JSON. To resolve this, please create a brand new connection following the instructions outlined in this documentation article .
If youâre facing any issues while creating your connection, please open a support ticket with our Care Team who will be happy to assist.
Thank you very much for your patience, understanding, and cooperation.
1 Like
Sorry Michaela, it was not an issue a week ago so something has changed either is everyoneâs WordPress worldwide OR in the module. Its very frustrating that companyâs just like to pass the blame off to someone else. There is a reason everyone hit the same problem at the same time!! We did not ALL just start doing the same thing incorrectly to cause the issue at the same time!
Can we get some honesty here please.
Hello @contentvault_content
Weâre very sorry for the frustration this situation has caused. I see youâve been in contact with our team through a support ticket. If you have any follow-up questions or if youâre still experiencing the issue, please continue the conversation in the ticket. Our Care Team has the necessary tools and information to further investigate this.
Thank you for your cooperation and understanding
1 Like
I was having the same problem and appears to be fixed after I whitelisted makeâs IP addresses for my region in my firewall.
I suspect for others experiencing this too, that there is a high chance they are getting html returned because of Cloudflare or an equivalent service running a check, which is causing the error.
You can find the IP addresses to whitelist for your region here: https://www.make.com/en/help/connections/allowing-connections-to-and-from-make-ip-addresses
1 Like