Does shorcut callback not work on MacOS?

I have a drafts action that runs another drafts action that runs a shortcut. I have the async enabled which works great on IOS. But on Mac OS it just times out.

Could you share the action? Hard to troubleshoot without seeing what you are actually doing.

I actually root caused, I was trying to quit shortcuts and the issue is it waits for the callback. Is there anyway to tell drafts the run was succesful without stop and output but then quit shortcuts?

What, exactly, are you trying to accomplish? If really can’t recommend an approach without understanding the task at hand.

basically, want to give drafts it callback on the success of a shortcut without relying on stop and output. E.g.

drafts5://x-callback-url/open?uuid=draftsUUID&x-success=shortcuts://

What is the end result you are trying to accomplish? I don’t think that is likely to be what you want.

In that example you are telling Shortcuts to open a URL that is an x-callback…which will open Drafts, which will process the /open URL, then open the x-success callback URL - which, in turn, opens the Shortcuts app. Shortcuts will go ahead and proceed with its next step after opening the drafts URL, thus quitting itself. Depending on timing, it may just get opened back up by the callback URL. I don’t think that’s what you want.

Are you trying to just end a shortcut by opening a draft in Drafts and quitting Shortcuts? In that case, just use Drafts’ “Open” shortcut action, then quit shortcuts. No need for a URL at all.

so basically i have a shortcut that hits the todoist API for bulk task creation just because the flow there was more intuitive. even if I open drafts at the end before quitting shortcuts, the action still appears to wait for shorcuts to respond that the shortcut was a success. If I have a stop and output, the action succeeds. But the issue is that stops and leaves the shorcuts window open on MacOS which is super annoying.

Probably could save some back and forth if you shared the action. I still don’t know what you have…is the Drafts action just a “Run Shortcut” action step that calls the shortcut? If so, what do you have “Return to Drafts” and “Wait for Response” set to on the step? Those would directly effect the behavior.

What’s the best way to share?

That’s exactly what I’m talking about, the wait for response. Basically, I want to give it the response without having to wait for stop and output. And this is because on Mac, want a step AFTER to close out the shortcuts window. What I did in the interim was duplicate the shortcut action and have one on mac and ios, turn the wait for response off for the Mac. But would be nice to have a flow that handles in case the shortcut doesn’t get a 200 code on its API call.

Could you just have a separate shortcut installed that does nothing but quit the app, then add a step at the end of your drafts action that is set to only be enabled on Mac that calls that other shortcut?

Yep, that saves me duplicating the action. Thank you!!

1 Like