Second brain systems that seem great until they randomly break

Second brain systems that seem great until they randomly break

Building a second brain sounds so clean in theory — just funnel all your thoughts, tasks, articles, and ideas into one magical space, then retrieve them instantly like your life has autocomplete. In practice, it feels more like maintaining a leaky boat full of sticky notes, half-finished Notion databases, recurring calendar block failures, and Zapier automations that stop firing on Thursdays for no reason. 😅

It gets especially weird when you realize: most second brain systems aren’t systems. They’re these janky improvisations of 10 apps taped together. And if one integration misses a beat? Your whole mental warehouse collapses into a pile of unread workflowy outlines and broken Airtable links.

Let’s talk about what these setups look like in real use — especially when you’re new and trying to follow someone’s ideal YouTube lifehack system, but none of the parts behave like they do in the tutorial…

1. The illusion of frictionless capture with mobile shortcuts

Everyone tells you to start with capture: “Create a quick way to jot down ideas anytime!” Which is solid advice until you’re deep in the woods trying to trigger an Apple Shortcut by voice while jogging, and Siri logs it as “Send content to Mom’s routines dot com” instead of “Send content to Notion.” 😛

On iPhone, I tried wiring up three different Shortcuts: one for notes, one for tasks, and one for random links. The idea was to use the Share Sheet, Quick Actions, and Siri — wherever I was, I could just swipe or speak, and boom, thoughts saved. But Shortcuts are moody. Sometimes they’d ask unnecessary permissions again (even though they were already granted), or just silently fail and dump me back to the home screen. No error, no message, just ¯\_(ツ)_/¯.

One time I whispered “add to Notion” while half-asleep in bed, and the Shortcut opened Safari for no reason and played a YouTube ad.

Tips that helped (after many fails):
– Do not trust iCloud syncing between devices with Shortcuts involving third-party APIs
– Use Reminders or Drafts as temporary collection buckets — they’re more stable
– Group your actions inside a single Shortcut with an ask-when-run menu (Not Apple’s best UI, but it avoids making too many individual Shortcuts)
– Never underestimate how often screen lock disables your auto-run triggers

This kind of capture tool looks magical in someone else’s TikTok. Mine mostly works now, but I’d say three out of ten daily entries still end up in the wrong place unless I manually check.

2. When Notion gets too clever and tags stop working

So you’ve got your daily notes flowing into Notion — nice. You clicked one of those trendy templates that comes with auto-linked databases, Status drop-downs, and a journal emoji that somehow shows the current weekday. It works flawlessly for six days and then suddenly breaks during a template duplication.

One very specific pain: when you update a Notion template to auto-tag new entries with the current month or a project name, it works fine *unless* you add the template from mobile. On my iPhone, adding from the Quick Add widget didn’t preserve the default tag properties. No warning, no red highlight — just blank fields. Add it from desktop? Works perfectly.

It took me actual hours to notice because the filtering views still showed the item… until I tried to roll up tasks by tag in a dashboard view. Then half the entries vanished and I thought the database got deleted. 😬

Also: Notion filters are unpredictable when you nest filters inside groups. You think you filtered for “March” but what you actually see is “all March items that also *don’t* have a status yet — unless they do, but only if they were created in nested templates.” Fun stuff.

Every time you fix one of these, another pops up. Data gets subtly lost or warped in a way that’s hard to spot until it derails your entire weekly review.

3. Why syncing between apps breaks right when you need it

There was a week where I happily set up Readwise Reader to sync highlights into Obsidian, pushed calendar blocks into Routine, and had Zapier append every new meeting to a Daily Log in Notion.

By Thursday: Obsidian stopped updating the new highlight notes (Readwise token needed to be manually refreshed but didn’t alert me), Routine started duplicating calendar blocks instead of moving them (Google Calendar API delay?), and the Zapier automation just… skipped Tuesday entirely.

Stuff like this happens constantly. What’s worse: there is often no alert. Nothing tells you something broke until you go look for a note and it just… isn’t there. So now I open a manual log every few days just to verify that the automations are still firing.

Literal quote from the email Zapier sent me:
> “This Zap didn’t run yesterday. We’re not sure why. Try turning it off and back on again.”

Coolcoolcool. Real second brain vibes.

Here’s one janky workaround I use now: I set up a synthetic test every morning. It drops a fake event, task, and note into my system, with a keyword like **”WORKFLOW_CHECK”**, and gives me a check signal later in the day if they were processed correctly. If any of the parts go missing, that’s my canary.

4. Zapier errors that technically shouldn’t exist anymore

Let’s talk about the gnarly underlayer of many second brains: Zapier. It’s the duct tape people rarely admit they’re using to glue everything together. And it’s also the first thing to silently break when something upstream shuffles their API.

Actual thing I saw last month: My “New completed Todoist task ➝ Append line to Notion database” stopped working. Zapier flagged no error. The task showed in Todoist. But Notion never got the line.

Eventually I discovered that the content of the completed task contained an ampersand. That’s it. “Read A&B article” caused the entire step to silently skip because the ampersand broke Notion’s internal property mapping via Zapier’s Notion integration. No red flag. No email.

I tested the same flow with and without the ampersand. Sure enough, the one with special characters failed, and the other worked normally.

Beyond that, Zapier’s “Formatter” app weirdly truncates text fields in certain cases where the input comes from an array — sometimes it just cuts off at around 1000 characters for no reason, even though the same text field worked fine an hour ago.

All this makes it feel like you’re babysitting your second brain more than using it. Sometimes I think of setting up a second second brain just to track issues in my first one.

5. Search always breaks when you need it the most

Congratulations, your notes are captured, tagged, sorted, and beautifully styled in an Obsidian vault, a Roam graph, or whatever you chose. Great. Now try finding that messy note about “the plugin expiration bug” you wrote at midnight last month.

You search “plugin expiry” — nothing. Then “plugin bug” — irrelevant. Then you try “Obsidian bug last month” and scroll through thirty unrelated quotes you clipped from newsletters.

There’s a painful truth here: unless you go *really* hard on metadata upfront (daily tags, topic categories, naming conventions), your second brain search becomes worse than Google. I’ve spent more time trying to locate things I clearly remember writing *somewhere* than I ever did just Googling similar info from scratch.

The one promising trick I use now: Obsidian’s Dataview plugin. You can write actual queries like `table file.ctime from “MeetingNotes” where contains(text, “plugin”) and file.day >= date(2024-05-01)`. Yeah, it’s basically writing SQL just to find your own notes, but damn if it doesn’t work.

Last week, I realized my Roam Graph had archived most highlights from my Readwise sync under the wrong date because my Mac’s clock had drifted by 10 minutes during a rogue spotlight reindex. So they were technically there, just invisible under the filters I thought were correct.

Anyway, I found them two days later — manually scanning the raw JSON 😐

A person looks distressed at their desk with their laptop showing an empty search bar, illustrating the frustration of search functionality failing at a critical moment.