Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jasonw's Achievements

Helping Hand

Helping Hand (3/5)



  1. would it be possible for Alfred to tell this keyword input is being used in the middle of a workflow and infer to have the option on / keep the window open? I have quite a few workflows like this and modifying / remembering to do this for each connection seems a bit laborious.. Most likely I am just being naive here -- if this generally brings better behavior, should this be the default..? On a different note, there is a help message under that check box but it isn't very obvious that it can help resolve such issues. Maybe the wording of that could be changed to make it easier for users to realize this? Thanks. -Jason
  2. Thanks @Andrew , yes, that did it. Works fine now even with stage manager on. I am ok to close this. And I apologize for the lack of details in my descriptions. Is it expected / required for similar workflows to select this when stage manager is on? It seems a little hard to "get" this from a user-experience perspective.
  3. oh I think I found the "cause".. it's stage manager. If I turn that off, it works fine now.. re: debug log, that's actually the entire log.. @Stephen_C does it still work for you when stage manager is on? PS. macOS version 14.4 (23E214)
  4. I sometimes use the "keyword" like this: listfiler -> keyword -> do task1 with the query passed from keyword -> keyword -> do task2 with the query passed from keyword -> keyword -> do task3 with the query passed from keyword now once the workflow reaches the keyword part, it stops prompting for the query. For example, this is the debug log for one of my workflow: [13:03:48.913] pytools[Conditional] Passing output 'sentry' to Arg and Vars [13:03:48.914] pytools[Arg and Vars] Processing complete [13:03:48.915] pytools[Arg and Vars] Passing output '' to Keyword what's expected is that alfred UI / box should appear and accept the query, and continue passing that to the rest of the workflow. But now nothing shows up. Pretty sure this was working before I updated to 5.5 beta. Could you help take a look or suggest other workarounds? Or let me know if anything needs clarification. Thanks. -Jason
  • Create New...