TStein

Recently updated to El Capitan 10.11.2 and Alfred 2.8.2 build 483. Now there is a noticeable delay after invoking Alfred before it will accept characters typed. I'd say about 3 seconds. This only happens after I haven't used Alfred in some time. So, for example, I might wake my Mac from sleep in the morning, invoke Alfred, then notice the delay. After that, there is no delay. However, if I don't use Alfred for a while, then the delay returns. I has an unfounded suspicion that this has to do disk activity, but not sure. Also, this is new behavior since the OS upgrade. Any suggestions?

What you were doing when the issue happened After not using Alfred for a while (minutes? haven't timed it), when first activating (cmd-Space), Alfred is unresponsive. The entry window shows up, but keystrokes (and results) don't appear. It is evidently accepting keystrokes (but misses some?) because after 5 to 8 seconds or so it wakes us and echoes what I've typed. Whether you were able to replicate it a second time by performing the same action Yes, replicable easily. Include any screenshots that might help us (n/a) Include the Alfred version & build number you are using V2.1.1 (227) Include your OS X version 10.9.1

Didn't Alfred used to remember the current search, so that if you searched for something, took some action, then re-called Alfred, your old previous entry was still there? I find that seeing a blank field is both surprising (making me think it used to be more sticky) and annoying, since I have to retype my search (or calculation, or whatever I'm doing with Alfred).