I’m sure this has been asked and answered already, the forums I found kind of explained this.
I have a shortcut that counts my completed iOS reminders from the day and adds that number to a goal. I have it running on an automation, once a day.
Some days it works some days it doesn’t. I don’t know what I’m doing; it makes sense to me if it works one day it should continue to work indefinitely.
I know it’s not working because I get the following error.
“No goal that sounds like [goalname]”
?!?!!?
Very strange error message to me. When that field in the Beeminder shortcut/action is blank, it is asking for the goal “slug”, I thought that was the goal name.
Definitely user error, but I don’t know what to ask to find the solution.
Goal name is the slug as it is called in the API documentation. Looking at your goal via the website, you would see something like https://www.beeminder.com/{username}/{goalname}, where you would see the goal’s slug aka goal name.
How about verifying that you are logged into the Beeminder app into the account that has the goal named do.
The error message about “no goal that sounds like” I think is related to the custom intent (this add data shortcut action) being configured to be eligible for Siri. It probably means, in this context, no such goal with that name was found.
I myself am not using this add data shortcut action. Before that existed I created a shortcut to add data using the API and have several other shortcuts that use that. Here is another post where someone showed how to use the API via shortcut: iOS Shortcut Integration - #7 by skorytnicki.
Yes, logged in to the iOS app. I am actually able to add data to the goal manually via the app, does that make a difference?
Thanks, I tried that shortcut too, and I want to say to the same mixed results. I thought my current method would have fewer opportunities for user error. I’ll give it another whirl tonight or this week.
Thanks, yep everything’s set, nothing to show when running and allowed to run when locked. It’s running at the prescribed time, just giving that error at the Beeminder action step
Not trying to spam anyone just another data point; I just switched it back from the api url to just the goal slug (exactly like it was before) and it just ran no problem. I have no idea why.
Note that I did run it manually, the automation runs at 10:30pm (so i guess I’ll need to remove that duplicate data point when it runs tonight)
I also have no confidence it’s going to continue working flawlessly, but I’ll try to keep you posted.
It turns out this is the only error the iOS app knows how to generate for shortcuts, so it produces this message no matter what has gone wrong. Could be you didn’t have internet, or beeminder was having downtime, or something else. You’ll still get this (often untrue) error.
More data; shortcut started failing again yesterday, nothing changed on my end. I’m going to derail tonight if this doesn’t decide to work in the next 2.5 hours.
