<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=550758) </details> <!--IssueSummary end--> {width=362 height=251} As @skarbek suggested > I need Duo to tell me what to do. If we suffer a failure, maybe put a button to forcibly reload the extension. Maybe link to troubleshooting documentation. Maybe auto-retry. > > We need to account for persons that are not only using Duo for the first time, but maybe also VSCode. They won't know how to reload extensions. A blanket error message is completely useless. We need to make the journey for day 0 users easier.