When a limit is probably expected
An expected limit usually matches the current launch scope, has cautious wording elsewhere in governed help, or depends on functionality that has not been claimed as fully live yet.
A limit is more likely expected when the product is being honest about thin coverage, staged rollout, or the need for human review before higher-confidence workflow depth exists.
When it looks more like a bug
Treat the issue more like a likely bug when the current experience appears inconsistent with the intended path, breaks unexpectedly, or blocks a step that governed help suggests should already work.
You do not need total certainty before reporting it, but you should preserve what happened instead of assuming every product gap is a defect.