Appeal open 3+ weeks with no response, dashboard blocks resubmission. Requesting a status check (case 6-1686000041488)
24 views
Skip to first unread message
Rob J
8:46 AM (8 hours ago) 8:46 AM
to Chromium Extensions
Hi all, hoping someone from the Web Store team can help me get unstuck.
My extension "Productivity Blocker" (item ID: dnodlniomejnjijbgcbdofpcblofldpk) was removed under the Spam and Placement policy (violation reference: Yellow Nickel). I filed an appeal on June 17, 2026 (case 6-1686000041488) and have had no response in over three weeks. The dashboard shows the appeal as still pending and blocks me from submitting a new draft, and the One Stop Support form routes item enforcement issues back to that same (now inactive) Appeal button. So I have no way to move this forward.
I'm not looking to re-argue the case here, just to get it looked at. Here is the one technical point I think may have caused a false "non-functional" reading: the extension's blocking is scheduled to the user's configured work hours (default 9 AM to 5 PM local). Outside that window it intentionally does nothing, so an automated or quick manual review performed out of window would see no blocking. Setting Work Hours to 00:00 to 23:59 in the options page demonstrates every feature in under a minute.
Could anyone from the team check the status of this appeal, or point me to the right way to escalate it? Happy to provide anything needed. Thanks for reading.
My extension "Productivity Blocker" (item ID: dnodlniomejnjijbgcbdofpcblofldpk) was removed under the Spam and Placement policy (violation reference: Yellow Nickel). I filed an appeal on June 17, 2026 (case 6-1686000041488) and have had no response in over three weeks. The dashboard shows the appeal as still pending and blocks me from submitting a new draft, and the One Stop Support form routes item enforcement issues back to that same (now inactive) Appeal button. So I have no way to move this forward.
I'm not looking to re-argue the case here, just to get it looked at. Here is the one technical point I think may have caused a false "non-functional" reading: the extension's blocking is scheduled to the user's configured work hours (default 9 AM to 5 PM local). Outside that window it intentionally does nothing, so an automated or quick manual review performed out of window would see no blocking. Setting Work Hours to 00:00 to 23:59 in the options page demonstrates every feature in under a minute.
Could anyone from the team check the status of this appeal, or point me to the right way to escalate it? Happy to provide anything needed. Thanks for reading.
Reply all
Reply to author
Forward
0 new messages