Hi.
I have upgraded everything and my daily note has stopped working.
I have a dictionary in my Apple Shortcuts script, basically stolen from the official example from a few years ago (structure wise). I changed the calls to remove the deprecated calls and now everything is getting dumped into the front matter, where there are not “replacement strings” and my logstravaganza output starts with a heap (100?) lines saying
{“timestamp”:“2025-05-23T01:35:03.017Z”,“level”:“fatal”,“sender”:“(undetermined)”,“args”:[“Uncaught (in promise)”,“@\nupdatePropertiesPane2@\n@\nupdatePropertiesCommands@\n@\n@capacitor://localhost/app.js:1:759836\n@capacitor://localhost/app.js:1:759774\n@capacitor://localhost/app.js:1:1953134\n@”]}
Additional information, when I trigger the actual command from Periodic Notes to open the daily note, via the command palette, it creates the base file properly with the right template. So Its somewhere after that in the chain, that it basically takes my whole dictionary of replacement keys an dvalues, and coverts them all to front matter…
Thanks for the report, @PeterFInBrisbane. Which action do you use in your Shortcuts workflow?
Because if it is one of the “… Periodic Note” ones, these have been deprecated for a while by now and will be removed in the upcoming v2025.1.0 (out within the next few days, App Store review permitting).
No I updated my code to use the new calls.
So I go, Create Daily Note in value PJF
Then I have a big dictionary that sets up all my %%Steps%% stuff mapping it to variables I have pulled together earlier in the script.
Then repeat with each item in Keys
Insert test Replacement at the placeholder placeholder in the Daily Note in vault PJF
So it is the insert text that is struggling. And it may be because I am giving it bad data…
If I just do the one substitution as shown in the above picture it works. If I do it like the following picture… then it all goes into the front matter
No I updated my code to use the new calls.
Yes, you’re right, you’ve mentioned that in your initial post, which somehow escaped me, apologies.
I’ve tried to reproduce the issue and came up w/ that stripped-down test case:
This is the whole of my current daily note:
---
tags:
id: 01JV9K2XF96HPK9XJ8J3YWZAW2
---
### Today is Tuesday, 2025-05-23
%%one%%
%%two%%
And that works fine. 
So it is the insert text that is struggling. And it may be because I am giving it bad data… […] If I do it like the following picture… then it all goes into the front matter
You might be right, and there’s something about your data. Hard to tell from afar, especially w/o access to said data and your DN template. So let me throw some random questions at you in the hopes to hit jackpot 
-
Could it be that some of the replacements are triple hyphens which Obsidian then interprets as YAML boundaries?
-
Some of the keys look weird (%, %%Cycle), did Shortcuts cut them off in the display or are they supposed to look like that?
About 8000 changes and its working again. I am not sure how I broke it. And am even less sure how I fixed it. Thank you for humoring me.
And in case no one has said this lately, Apple Shortcuts scripting, the environment, the inability to develop things that run the same on the large screen of my mac and the iphone (think health, think other custom apps on the phone), the whole thing is genuinely so bad, so ugly and so unloved by apple. argh…
About 8000 changes and its working again. I am not sure how I broke it. And am even less sure how I fixed it. Thank you for humoring me.
Sure thing!
And in case no one has said this lately, Apple Shortcuts scripting, the environment, the inability to develop things that run the same on the large screen of my mac and the iphone (think health, think other custom apps on the phone), the whole thing is genuinely so bad, so ugly and so unloved by apple. argh…
Yes, it could be better. By a lot.
