They appear regularly and many go unanswered. In many cases a verification input is wrong: solc version, optimization settings, different source code, constructor parameters; and in a very few cases it is something wrong on Etherscan side.
Usually possible answers are specific to the contract deployed and they might not work for a different contract. Also having a lot of similar questions makes it harder to find an answer that might work in a particular situation.
- Closing them as a third party issue.
- Chose a question with general instructions, and mark new question as a duplicate.
- Do nothing.
- Do something else.