Need help: Verification failed updating a published CyberBrick project

MakerWorld MakerWorld General
1

Hello MakerWorld Team,

I hope someone from the Verification Team or the MakerWorld Team can help point me in the right direction.

I am the creator of the following published CyberBrick project:

Project:
https://makerworld.com/en/models/3075223-yl_rc-water-cannon-yl_rc-water-turret#profileId-3462568

The project was successfully reviewed and published, and it has been working normally since its release.

On July 23, I submitted an update to this existing published project for review.

The update only included:

  • Revising the BOM to recommend the official Water Turret Hardware Bundle together with a small number of additional components (such as the 360° rotation servo), making it easier and more affordable for users to obtain all the required parts.

  • Replacing one demonstration video.

No STL files, model geometry, functionality, assembly, or project structure were changed.

On July 27, I received the following verification result:

“Verification failed. Please try again.”

(See Screenshot 2.)

The original published version remains online and fully functional, but this update cannot be approved and published due to the verification failure.

I have already contacted MakerWorld Support (Ticket MU260727306002). However, I believe my case may have been misunderstood as a browser or upload issue, while the actual problem appears to occur during the verification stage when updating an already published project.

I completely understand and respect the verification process, and I am not asking to bypass it.

I would simply appreciate it if someone from the Verification Team could review this case, or let me know whether this is a known issue affecting updates to existing published CyberBrick projects.

If any additional information, logs, screenshots, or testing would help identify the cause, I would be more than happy to provide them.

Thank you very much for your time and any assistance.

Attachments

Screenshot 1
The published project page, showing that the project has already been successfully published.

Screenshot 2
The verification result received on July 27:

Figure 1 – The project has already been successfully published.
Figure 1 – The project has already been successfully published.1810×947 268 KB

Figure 2 – Every update fails with Verification failed
Figure 2 – Every update fails with Verification failed1187×625 56.7 KB

“Verification failed. Please try again.”

2

Yep. Seen this too. You aren’t alone.

Whenever you submit a model to be verified - even if you only changed a word in the text - everything goes through the regular verification process.

You must have something that is no longer compliant in there. And if it’s being rejected, it pretty much means the model is somehow actually invalid for users that download it too.

It would be way better for us if only the things that changed got verified on a resubmission but I can also see Bambu’s reasoning.

Where I saw it was with some Studio updates, how it handled prime towers changed. The change meant my prime towers then interfered with the actual print object so it would notice that and reject.

Some changes Bambu makes can in effect invalidate whole swaths of models people have uploaded. It’s very frustrating. Instead of versioning and grandfathering deprecated features, they just go with whatever is latest.

Creators have to chase changing requirements and users who download models that would no longer verify may find it doesn’t print well or doesn’t print at all. And that reflects on creators because most who just download won’t have a clue that the model used to print properly.

Changes that invalidate previously successful models need to be accommodated with versioning.

4

At first, I thought the STL might be the problem, but since it was explicitly stated that nothing had changed - except for the video!

The verification process for videos was recently changed. Presumably, the online verification system thinks you’re violating the rules. This may be a false alarm.

Please check to see if you’ve followed all the current rules and guidelines regarding video uploads - they’re much stricter now.

Screenshot 2026-07-29 222823
Screenshot 2026-07-29 2228232580Ă—717 89.8 KB

5

Thank you very much for your suggestion!

That’s an interesting possibility, and I wasn’t aware that the video verification process had become stricter.

The update actually included both a revised BOM and one replaced demonstration video, so at this point I’m still not sure which part triggered the verification failure.

I did review the video carefully before submitting it, and I don’t believe it violates the current guidelines. However, if you have a moment, I’d really appreciate your opinion.

This is the exact video that was included in the update:

https://www.youtube.com/watch?v=DxpuXUzxAWg

If you notice anything that could potentially trigger the verification system, please let me know. I’d be very grateful for your feedback.

Otherwise, I’m hoping someone from the Verification Team can help identify the actual cause.

Thanks again for taking the time to reply!

6

Thank you for sharing your experience! That’s actually very helpful.

I understand what you mean, and it makes sense that the entire project goes through verification again, even for a small update.

What puzzles me is that I didn’t change any STL files, print profiles, assembly instructions, or the project structure. The update only included a revised BOM and one replaced demonstration video, while the original project is still publicly available and working normally.

If the project no longer complies with a new requirement, I completely understand that. I just hope the verification process can identify which specific part is causing the rejection, because at the moment I have no indication of what needs to be fixed.

Thanks again for taking the time to explain your experience—it definitely provides some useful context.

7

The video is definitely 100% in compliance with the rules.

You never know why a photo or video has been rejected. Now that the rules have been updated, it’s even harder to tell. Who knows what might be troubling the verification AI? Is it even the video itself?

Perhaps there was too much green in the video because it was filmed outside? Or maybe it was too long? Or maybe they don’t like the format?

The only thing you can do is edit the video differently and try again, and again, and again…

8

Thank you so much for taking the time to actually watch the video and check it yourself—I really appreciate it!

Your feedback is very reassuring. Since you don’t see any issues with the video, I’m now even more convinced that the problem may lie somewhere else in the verification process rather than the video itself.

Hopefully the Verification Team can identify the actual cause, because without any indication of what failed, it’s very difficult for creators to know what needs to be fixed.

Thanks again for your help and for sharing your thoughts!

9

We had an issue with AI images and renders so Bambu decided to change the rules on images in model profiles. All I did to get caught up in it and have to resubmit models was to delete rendered images in my models. Not even a change to a model. Just deleted images forced resubmissions and full checks.

All my prime towers on build plates then were tripping up the submission because they started encroaching the prints and there was no way to make them fit on the build plates due to the new format. I had to re-open all my 3mf files that were affected and delete the prime towers in order to comply with the no renders ruling.

The renders I had to delete? All supplied by Bambu of the individual build plates when I first uploaded the files. It used to be you could add those in to help people visualize prints your models would make.

So definitely hear you on it not even having anything to do with the models themselves. That’s why Studio needs to version stamp 3mf files and certain things need to be accommodated. The formatting of prime towers, for example. Had the upload checker known my prime towers were all the old format, they should have just been checked against the old format and anyone using a new version of Studio to open them should see the prime towers as originally included in the print.

As the model collections get bigger, Bambu really needs to change this approach.

10

Thank you for sharing your experience in such detail. It really helps put things into perspective.

Your examples make a lot of sense, especially the part about having to update projects because of changes introduced after they were originally published. That seems very similar to what I’m experiencing now.

I also agree that versioning would make the process much more creator-friendly. If an existing project needs to comply with new requirements, that’s understandable—but creators should at least know exactly what changed and which part needs attention.

Thanks again for taking the time to explain all of this. I really appreciate hearing from someone who’s been through similar situations.

11

I don’t know if this applies to your case, but in MakerWorld, if you change a file your have to also change its name or MakerWorld will have problems with it. If your video has the same name as before, it will confound MakerWorld.

12

Thanks for the suggestion! I really appreciate it.

In my case, I don’t think it’s related to the video filename. I didn’t replace an existing video file—I uploaded completely new videos to YouTube and Bilibili and updated the project with the new links.

Also, the submission itself completed successfully and entered the verification process. The update wasn’t rejected until four days later during verification, so it seems more likely that the issue occurred on the server-side verification rather than during the upload.

Still, thanks for sharing your experience. I’ll keep that in mind for future updates.