I spent hours debugging a Confluence automation — turns out my prompt was too long 🤦

[#1]

A hard-won lesson about the 30-second wall, and how to work around it.

I've been working on automating SEO audits in Confluence. The idea: add a label to a page, trigger an automation rule, and have my cloud AI agent review the content and post a comment with the full audit.

Simple enough on paper. In practice? I spent way too long staring at error messages and wondering what I was doing wrong.

Here's what actually happened — and what I wish someone had told me before I started.

🛠️ What I was trying to build

The setup I had in mind:

1. Someone adds an seo-check label to a Confluence page
2. A Confluence automation rule fires and sends the page content to my AI agent via a Send web request action
3. The agent runs a full SEO audit against my playbook and posts the result as a page comment

The agent itself worked great when I tested it directly. The audit output was exactly what I wanted. So I wired it up in Confluence automation, tested it… and nothing. Literally, a blank page comment:

🐛 The debugging spiral

I tried everything I could think of:

• Checking my API endpoint and authentication headers
• Simplifying the JSON body of the web request
• Switching between POST and different content types
• Testing whether the automation rule was even firing correctly
• Rebuilding the rule from scratch

Sometimes it worked on short test pages. Sometimes it just silently failed. I could not figure out the pattern.

Then I noticed this message in the automation audit log:

30 seconds. That was the key.

⏱️ The 30-second wall: a known platform limit

Confluence Cloud automation's "Send web request" action currently has a fixed 30-second timeout. This is not a setting you can change today. Atlassian has an open suggestion requesting a configurable timeout, which confirms that the current limit is fixed. If the endpoint takes longer than 30 seconds, the automation can time out and return a message saying the result is unknown.

---

Why does this matter for AI agents? A good AI audit isn't fast. My agent reads the full page content, runs it through a multi-step framework, and generates structured output. That easily takes 30–60 seconds — sometimes more for a long page. The automation fires, the agent starts working, the clock runs out.

---

💡 Where I've landed (not a perfect fix yet)

The first thing I tried was simplifying my prompt. I stripped it down to almost nothing — just enough to call the agent. It worked… but the output was useless. A shallow, generic audit that missed everything I actually cared about. So that wasn't a real solution.

What I ended up doing is moving the system prompt into variables — {{anthropicPrompt}} and {{seoSystemPrompt}} — and keeping the request body as light as possible. That combination gets the request through within the 30-second window.

It works. But it comes with a real tradeoff: the lighter the prompt, the shallower the audit. I'm essentially tuning the instructions to fit a time constraint rather than to produce the best output. That's the part I haven't fully solved yet.

So if you're trying to do something similar — this is the workaround that gets you moving. Just know that you're trading depth for reliability, and the 30-second wall is still there whether you can see it or not.

Have you run into this timeout issue in your own Confluence automations? I'd love to know how you worked around it — drop a comment below 👇