SOLVED

Unable to post, flooding error

Brass Contributor

I have just wasted 2 hours trying to post an Intune question , 2 questions actually.

I kept seeing errors like this thread https://techcommunity.microsoft.com/t5/tech-community-discussion/can-t-post-receiving-post-flooding-...

 

It turns out the error messages mention a non-existend "Save" button for saving drafts, and then tell the user they are rate limited for 300 seconds even after they have waited 6 minutes. The error messages are just random garbage and not at all useful, and all because I had merely not added a tag to my post. It would, be great if someone on the Software Test team had a look at and got this fixed so that the error message correctly admonishes users for not tagging, because the error message wasted a lot of time and I even deleted my account and created a new account over this poor experience. Hope this can be solved as it's a long running defect that discourages people from participating, and as a Software QA myself makes me want to never seek a job at a company that treats quality this way.

As I write this I'm still seeing a message telling me to "Save" my post using some invisible save button.

Thanks. Screenshot 2024-01-15 193458.png

3 Replies
best response confirmed by Conrad_Braam (Brass Contributor)
Solution

@Conrad_Braam 

 

Thank you for the feedback, we have captured it and will consider it in a future version of the community UX. The issue with the 'save' message is caused by the fact we have customized the user experience to encourage users who are writing blog posts to save regularly as blogs tend to take longer to compose than forum posts. Unfortunately the current version of the platform doesn't allow us to have a different 'auto recover' message for forums than blogs.

 

We are planning to overhaul the community UI / UX this calendar year.

 

The flood protection error you hit is designed to protect the community from new users spamming the community but I think you feedback about labels is also valid and is something we have already seen fixed in the new UI/ UX Coming this year.

 

Please do not delete your account just to try to get round this issue, once you close your account you can't then re-register with the same account for 72 hours.

 

Please accept my apologies for the poor experience you have experienced with these two posts.

OK, so this is a new regression. Not long standing. That is good.

I have a fair number of email boxes, so deleting my account was not a real pain, but I was that frustrated that I had to try it to see if it was my browser causing it. People do crazy things when they are in a rush or unhappy. It's really hard to cover those situations even with excellent working technology to be fair. Now to get my intune question posted in.
Thanks Allen

@Conrad_Braam  Hi,

Thanks for reminding me of my first replies, I also deleted my account :)

Good luck!

1 best response

Accepted Solutions
best response confirmed by Conrad_Braam (Brass Contributor)
Solution

@Conrad_Braam 

 

Thank you for the feedback, we have captured it and will consider it in a future version of the community UX. The issue with the 'save' message is caused by the fact we have customized the user experience to encourage users who are writing blog posts to save regularly as blogs tend to take longer to compose than forum posts. Unfortunately the current version of the platform doesn't allow us to have a different 'auto recover' message for forums than blogs.

 

We are planning to overhaul the community UI / UX this calendar year.

 

The flood protection error you hit is designed to protect the community from new users spamming the community but I think you feedback about labels is also valid and is something we have already seen fixed in the new UI/ UX Coming this year.

 

Please do not delete your account just to try to get round this issue, once you close your account you can't then re-register with the same account for 72 hours.

 

Please accept my apologies for the poor experience you have experienced with these two posts.

View solution in original post