Futures

Was refactoring a task today with Claude, and it nearly deleted a custom event subscription before I caught it. Claude saw that the event wasn't called anywhere in Mechanic and thought it was a mistake, but the event subscription was a webhook topic and it just couldn't see it. Adding a way to look up webhook information would be useful, and would avoid situations like the one I ran into.

When a Shopify action runs a GraphQL mutation, Mechanic checks the response for a non-empty userErrors array. When one is present, the action fails — the error shows up in your run log, and mechanic/errors/action fires so error-handling tasks can respond. Shopify has been migrating mutations to more specifically named error fields, and deprecating plain userErrors on those mutations. For example, orderCancel now reports errors via orderCancelUserErrors, and productCreateMedia uses mediaUserErrors. Mechanic currently only recognizes fields named exactly userErrors — so if your mutation selects only the newer field name (which is what Shopify's docs now recommend), errors can come back in the response while the action still reports success. This request: teach Mechanic to recognize these renamed error fields (they all end in UserErrors) so they fail the action just like plain userErrors does today.

I've been using {% break %} to end my task runs early (like a sys.exit in Python), but I just realized that it's not written anywhere in the documentation that this is an official way to stop executing task code. It's pretty useful to have this. If this is the intended behavior, could it be added to the documentation? And if not, then my feature request is for a command that halts a task early. Thanks!

It would be really helpful to see when task runs are completed and won't create any more actions, without having to click into each task run manually.

I'm working on connecting the CLI up to VSCode, and I want to enable live task previews as the user is working. Currently the CLI can only read from files on disk, so before the preview can be updated the task file needs to be saved to disk. Adding a --stdin argument to mechanic tasks preview would allow me to bundle the unsaved task file in memory and pass it directly to the CLI. That way, I can avoid the need to autosave the task file as the user is working, which feels rather intrusive to me.

I've been working on connecting up the CLI to VSCode, and I'm always using the --json argument to ensure I get complete, structured data. In case of errors though, the command output goes to stderr instead of stdout and is usually (always?) a string instead of json. I'm hoping for a more stable way to identify these error message types, rather than matching on individual words or phrases that may change in the future. For instance, when publishing a task if there is a conflict I want to detect that and offer to open up the diff editor. But right now, I'm matching on an error string that could change. Perhaps exiting with standardized error codes? eg. 2 - remote conflict 3 - task not found 4 - auth failure It looks like pull already uses exit code 2 for conflicts, so this system could possibly be expanded to cover to all errors. I'm not sure if it would make sense to format stderr as json when the --json argument is passed, but maybe that's also worth considering.

This would be a very useful feature, on par with the platform auto-handling of rate-limiting of graphQL queries. https://usemechanic.slack.com/archives/CURE65U2W/p1778629608131149

An implementer wrote in: > on the event action run details page where it shows all action runs, in some cases thousands. It would be really helpful to be able to filter this to Errors Only. It's currently quite difficult to find the error.

Shopify now recommends it over md5 and sha256. https://shopify.dev/docs/api/liquid/filters/blake3 https://shopify.dev/docs/api/liquid/filters/sha256 https://shopify.dev/docs/api/liquid/filters/md5

"wish there was a way to prevent certain users from accessing Mechanic tasks to edit, but enabling them to trigger tasks (e.g. from "More actions > Send to Mechanic")" https://usemechanic.slack.com/archives/CURE65U2W/p1709118096974909