Andrew

@luckman212 could you try typing 'reload' into Alfred to clear his caches? Cheers, Andrew

Just for additional info, this is the output I get when testing on 10.14.6 with the in keyword, and filenames matching what you've suggested:

@ggggg I know that Big Sur is having issues indexing RTF files, but you're using 10.14: https://discussions.apple.com/thread/252144688 Could you please try the same test with plain text (.txt) files. Again, Alfred isn't in control of these file results, so if we can identify the underlying issue on your Mac, it should give us a solution. Also, next time, could you post the full output of Alfred's troubleshooting, as this can also give additional context which can help identify issues. Cheers, Andrew

@Benben Alfred has to use the clipboard to paste text, however, there is an option to restore the previous clipboard content in the Advanced prefs:

Alfred uses the macOS metadata index for internal file search, so I'd be interested in knowing what Spotlight's behaviour is for you. Does Spotlight find the files by content in these scenarios?

Numpad features have been added in Alfred 4.5, both recognising and dispatching numpad keys, and new popup menu options on the key combo editor for adding numpad keys on a Mac which doesn't have a numpad. Let me know if you have any issues

Ooops! Thanks for spotting

@danielgomez22 Alfred stores the clipboard history locally in your home folder in this location: ~/Library/Application Support/Alfred/Databases/clipboard.alfdb If you quit Alfred and copy this from your old Mac to new Mac (or copy this from your backup), then Alfred should see your previous clipboard history again Cheers, Andrew

@GuiB if you update to b1252, the Keywords and Script Filter actions will only now correctly be added if there is a single argument. I have also made the types (files, urls, text) ticked by default for new Universal Action trigger objects, as this is the more likely case of "show for everything", and makes it less likely to forget to tick any of them and wonder why the action isn't showing at all.

@GuiB Ah you're quite right that there is a mistake in the default adding of workflow Keywords and Script Filters. These should only be seen in Universal Actions when there are single arguments. I'll fix this

This is exactly why you need to work out if your workflow is compatible and configure appropriately. If you connect the output of a Universal Action trigger (or any trigger with multiple items) into a Run Script or Script Filter, you'll get each item as a separate argv argument. If your Script Filter isn't compatible with that, it's best to set your Universal Action trigger to a single item only. I'm seeing both URLs open with Safari. What browser are you using?

I've just put b1250 pre-release up which refactors a few things to streamline the framework. I'd appreciate if people could report back that Universal Actions is still working as before, as we are getting close to general release on this. The update makes a few improvements to type recognition, and type "forcing", so that would be a good place to test. @GuiB one small improvement has been added which relates to something we were discussing, where Alfred will now prefix with https in the case of forcing the type to URL and no scheme existing. So now you should be able to say... "alfredapp.com" as type "url" and it will work. Let me know how you get on

Just a quick note to say I'm watching this discussion, and am happy to take the experience and advice demonstrated here if it leads to a change / improvement in Alfred

@deanishe external triggers don't get migrated from the current version of a workflow, as they are treated as intrinsic to the workflow being installed / updated. This means that if a new version of a workflow being installed deliberately changes the external IDs to suit its internal purpose, then they will work as expected.

The context is different here as Alfred's default results can very loosely match a URL without affecting the other results. If a URL match happened in Actions, then it may filter out actions when it shouldn't. What I may look into is loosely matching URLs if the requested type is of "URL" by automatically prefixing https.