[Original title: When customizing packing slip templates using Mechanic, is it possible to have a button appear on the main orders screen of Shopify that will create packing slips for the orders I select?] After looking online for more customized packing slip solutions on Shopify, I saw Isaac wrote this: "Mechanic ( apps.shopify.com/mechanic ) is able to generate PDFs for any purpose, with any content, using any data available via the Shopify API. This includes metafields, and also fulfillment location information (which Order Printer doesn't have either, from what I understand)." My question is if I went with Mechanic to customize a packing slip, can I have a button appear here that will create packing slips for the orders I select?

Currently, formatting a phone number into a human readable format takes quite a bit of work. You have to strip out any non-digit characters, and then split the remaining digits into individual characters and output them one by one. It’s also prone to errors, as you can only support one phone number format this way. The e164 filter is useful for getting the phone number into a standard machine-readable format, but it’s not great for user-facing tasks like invoice generation. Implementing something like number_to_phone in Rails would make this kind of user-friendly formatting far easier.

It would be helpful to have the option to get notified in the event of a task or event failure. Ideally email or text,

If I'm running a scheduled task every 10 minutes, I want to be able to auto-cancel (or auto-pause?) subsequent runs if one run is still being performed.

Background: Currently using Email with PDF attachment to send Tax Invoices to customers, this is automated but often customers input incorrect emails, or because its a tax invoice, need the email to be resent to the an alternate address. Current workaround is to copy JSON data into a blank task but the ability to Edit & Trigger would be beneficial here. https://usemechanic.slack.com/archives/CURE65U2W/p1660605164077839

When navigating to Events for a Task, you can click "Load more events". I needed to do this, as I'm debugging an issue with a task that has a delay of 14 days after fulfilment on it, so I have to go back through the history to see the logging. This means I have to click "Load more events" several times to get to my event. The frustrating thing is, once there, if I navigate to another tab, then click back, the list will reset back to the initial page of events again, this is without any interaction from me. So I am forced to click "Load more events" many times again to get back to where I was. Firstly, it would be great if it didn't do that. :-) Secondly, it would be really great if there was a time/day filter. So you can view just the events from the timeframe in question.

I'd like to create a task that will email me details about any error that I generate using the {% error %} tag. I could create a custom task to do the emailing and before any {% error %} tag I could have it trigger the custom task, however that means updating a lot of tasks with this new code. Would it be possible that Mechanic could trigger a standard error topic and provide the error JSON and related event/action data? That way I could leave all my existing task code and just hook into the topic.

Having task options field types that exposed object pickers (product, variant, etc.) would be a nice feature for merchant configuration of tasks.

For the most part, it doesn't matter if Mechanic's tasks are somewhat delayed sometimes. However, when building tasks that directly interact with the shop's storefront, it becomes much more important that the task run as soon as possible, if not immediately. Taking into account good practices of letting the customer know that they need to wait for the task to complete, it would also be helpful if there was a way to prioritize tasks like this. Tasks with prioritization would be pushed to the top of the task queue (after any other prioritized tasks), allowing less time-sensitive tasks to run afterwards. The level of granularity to this prioritization is up to debate, but it should probably be kept simple so as not to get confusing or hard to manage.

Currently, to use a webhook in a task, the process is to: Leave the task to create a webhook Copy the webhook url and webhook topic to your clipboard (if you have multiple clipboard item support), or copy to a text document for reference. Return to your task and paste the two options into the task. It would be great if there was a task option which created a populated dropdown list of existing webhooks in the store. This would be especially useful in reducing the friction of setting up library tasks which require webhooks. (PS - Even better would be if the webhook could be created right from the task creation page, but that's an additional enhancement I'll leave for later)