BUG: Flow Launcher doesn't finish indexing programs if spammed the shortcut key to launch it while it's starting

[rottakore]

Checks

• I have checked that this issue has not already been reported.

• I am using the latest version of Flow Launcher.

• I am using the prerelease version of Flow Launcher.

Problem Description

If you spam the Flow Launcher launch shortcut key (Mine is LWin) while it's starting, it will infinitely try to index programs without success. Most of the results will work but all applications will not show up.
Example, Vivaldi will not show up, Spotify neither, but if I search a Windows setting or anything else it will show up.

To Reproduce

1. Run Flow Launcher
2. Spam the launch shortcut key while it's opening
3. Try to search for any application

Screenshots

No response

Flow Launcher Version

1.20.2

Windows Build Number

10.0.26100.5074

Error Log

No error occurs.

[Jack251970]

Can you check if this can help?

https://ci.appveyor.com/project/JohnTheGr8/flow-launcher/builds/52743730/artifacts

[Jack251970]

@rottakore I am not sure if #3978 can help. Could you please check if this can help?

https://github.com/Flow-Launcher/Prereleases/releases/tag/v2.0.0.13849

[rottakore]

Sorry, I'm going to check.

[rottakore]

It still happens.

All programs disappear (and Flow Launcher keeps looping a loading bar animation below the search):

But every other result works:

Below images showing the correct results if I do not spam the LWIN to launch Flow Launcher while it's opening (If I wait for it to appear first then finally press the LWIN button):

[rottakore]

If I click "Reindex" it never ends reindexing too.

AND this is the FIRST time it's happening without me spamming the LWIN key while Flow Launcher is loading at system startup, so maybe this is not the reason for it to happen (but it's weird, if I want it to happen consistently I have to spam the LWIN key), but the problem seems to be in the "Programs" plugin specifically, not flow launcher itself...

The only solution seems to be restarting the computer or ending Flow at task manager then running it back again. Look, now it works.

[Jack251970]

Thanks for your reply! I think we need further investigation into this.

[Jack251970]

I observed that this problem seems to occur easily when Windows is resumed.