Search the Community

If you're having an issue with a workflow you've downloaded or one you're writing yourself, please follow these instructions. It will greatly increase your chances of getting a fast and useful response. It is extremely difficult to diagnose (let alone fix) a problem you're having unless we can reproduce it. If we can't, we're mostly just guessing. As such, it's very important that you provide what we need to do that, and post it in the right place. It can mean the difference between getting help within a few minutes and not getting it at all. Other people's workflows If you have an issue with a workflow you've downloaded, do the following: Make sure you're using the latest version of the workflow. The issue may have already been fixed, and it causes confusion if you are talking about a different version of the workflow to everybody else. Read the workflow's documentation and thread. If the workflow has documentation, read it. Find the workflow's thread and read at least the original post and the last few pages. It takes a few minutes, but it might take hours or days to get a reply on the forum. The lovely members of the Alfred community generously offer their software, expertise and limited time for free. Please respect that and do your best to avoid asking questions that are answered in the documentation or on the previous page of the thread. Do not start a new thread for your issue. It pollutes the forum, fragments the discussion, and depending on who wrote the workflow, the chances that the author will see your post range from excellent to almost zero. Instead, find the workflow's thread and post your issue in there. That way, the author (and other users of the workflow) will be notified of your post, and they're the best people to answer your question. If the workflow doesn't have a thread, it's likely the author isn't a forum member, and there's probably a better place to raise your issue (e.g. a GitHub issue if you got the workflow from GitHub). Provide a meaningful error. We can't diagnose a problem from "it's not working" or a screenshot of an error message in Alfred. Be specific. Use Alfred's debugger and post the output. If the workflow has a log file, include its contents, too (unless they're exactly the same as the debugger's). Remove any private data from debugger/log output before posting. You don't want to post your API keys or passwords on a public forum. Explain what you were doing. What did you click? What did you enter in Alfred? What did you expect to happen? What happened instead? Your own workflows If you're having a problem with a workflow you're writing, post the actual, non-working workflow. Upload it somewhere (Dropbox?) and post a link. Screenshots and code snippets are not enough. If we can't replicate the problem by running the workflow, we can only guess at what might be wrong. It is entirely unreasonable to expect us to try to recreate your workflow from a code snippet simply in order to help you. Post the broken workflow, so we can run it ourselves. It saves everybody's time. In addition, you should also post: The version number of: Alfred macOS The version of any non-system language you're using (e.g. nodejs) The version of any non-system programs you're using (e.g. ffmpeg or youtube-dl) if they aren't bundled in your workflow Any changes you've made to your macOS environment (e.g. via launchctl setenv) or the language you're using (e.g. via Python's usercustomize.py or sitecustomize.py files) It might not seem relevant, but if your workflow isn't working and you don't know why, you're likely not in the best position to determine what's relevant and what isn't. So just post the lot. It'll help you get an answer faster. Thanks to @vitor and @phyllisstein, whose earlier posts on reporting issues were consolidated into this one.

While this isn't strictly speaking a bug, I don't think when people select the "Recursive" option to "Act on directory contents" for the Automation Tasks of tags (e.g., Add Tags, Remove Tags, Clear Tags) that they intend this to apply to the contents of packages. For instance, if you use the "Add Tags" Automation Task, and select the "Recursive" option, when it's applied to an application, it will actually add the tag to the invisible contents of the application, too - which could cause problems, and seems like overkill. I'm sure there are a bunch of ways to fix this, but it'd probably be easiest to do a quick content tree check for "com.apple.package" - which is broad enough to catch applications, bundles, kernel extensions and most things you wouldn't want Alfred thumbing through - and to only apply/remove/clear the tags of children of files that don't contain it. In other words, if it's a package, Alfred should just behave as if the user had not selected the recursive option (i.e., applying/removing/clearing the tags of the package but NOT its children/contents). If you need any more info, just let me know. Cheers! PS: I'm on Tasks Version 2022.14 (Last Checked Sep 13, 2022, 4:06 PM) & Alfred 5.0.2

Environment I am using macOS big sur, 11.1 (20C69) and also the newest version Alfred 4.3.1. Problem snippet doesn't expand if there are characters before the keyword. For example: The snippets I using are \ue --> ü, \oe --> ö, etc to write German words. if I write \ue only, it will expand correctly, but when I write f\uer, it won't expand, and if there is a whitespace before the keyword \ue, it works. Others snippets also. Troubleshooting I have read the page https://www.alfredapp.com/help/troubleshooting/snippets/ and follow it to solve my problem. the only effect is to make the snippet working but still having the problem above. In fact, the snippets don't work completely before I did those things in the article. And also, Strangely, it doesn't work again for a while, when I writing this post. What I have done. Make sure that I have activated expansion in Alfred's preferences , set the snippets to auto expand and used the correct keyword Check cmd+v is still the way to paste. Check Accessibility for Alfred Kill Alfred completely and then remove Accessibility permission of Alfred and add again Test in several different app and make sure they are not using secure input to prevent Alfred to auto expand Change the option, simulated key event speed, I have tried all choices. check Others app which may be conflict with app. I don't use other apps which are about the clipboard and also text expansion.

I activate a List Filter in a Workflow with a Hotkey combo: and when I press option, "Search for '(null)' in Spotlight" is shown as the subtext of the action: Hitting enter opens a Finder window, but of course it can't search for "null". It seems like this behavior should be prevented?

Please see this thread in the Workflow Help & Questions forum.

When 1Password is locked on my machine the powerpack seems to work fine. It loads the site, and opens up 1Password mini in my menu bar and prompts for the master password. Once I authenticate it logs in as normal, works great. If I then logout of the website and try it again it opens the site in the browser and nothing more. Once I "lock" 1Password the functionality operates as it should for any website I have in my vault. Alfred - 2.8.2 (432) 1Password - 4.4.2 (442010) - Mac App Store OSX - 10.9.5 (13F1507) - Mavericks

RESOLVED: I had to check "with space" to differentiate two file filters with similar keywords (e.g. fc & fcf) or the results were always from the first keyword. Thanks to all for feedback and assistance. ------------ Original post ------------ Simple File Filter to Open File Workflow. When I use File Type = public.folder, the results include files from inside the folders and swamp out the folder results. Any ideas or is this normal? I have no idea if this worked in the last stable release as I never used this one before. My apologies if this has been covered but Google searches, the knowledge base and a quick scan of this form didn't reveal anything to help. Thanks, Mike