Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Trello Automation editor infinitely loads

Катерина Соловьёва
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 27, 2026

Trello Automation editor infinitely loads

Problem

I am unable to create or edit any Trello Automation. The Automation editor loads indefinitely and never opens.

The problem affects:

  • Rules

  • Due Date automations

  • Scheduled automations

  • Buttons

Reproduction

  1. Open any Trello board.

  2. Open Automation.

  3. Select Rules or try to create a new automation.

  4. The page remains on an infinite loading spinner.

The same problem occurs on a completely different board and with a different Trello account.

What I have tested

The issue persists with:

  • Google Chrome, latest version (152.0.7977.65)

  • Chrome Incognito

  • other browsers

  • a different Trello account

  • a different Trello board

  • a completely different Internet connection via mobile hotspot

  • Windows 10 22H2

  • cookies enabled for Trello/Atlassian

  • hard refresh with Ctrl+F5

The issue therefore does not appear to be related to a specific browser, Trello account, board, or Internet connection.

Technical information

Chrome DevTools Console shows:

Error, timeout while initializing index iframe for https://app.butlerfortrello.com/.../powerup-loader.html. Timeout=30000ms

There are also errors such as:

Failed to load resource: net::ERR_CONNECTION_RESET

In the Network tab, some Butler requests return HTTP 200, including:

  • powerup-commands

  • settings

However, the Automation editor still remains on the loading screen.

I also tested connectivity from Windows Command Prompt:

ping app.butlerfortrello.com

Result: 4 packets sent, 4 received, 0% packet loss.

curl -I https://app.butlerfortrello.com

Result: HTTP/1.1 403 Forbidden from Amazon CloudFront/S3, meaning the server is reachable.

The Trello CDN test page also loads successfully.

Expected result

The Automation editor should open normally so that I can create or edit automations.

Actual result

The Automation editor never finishes loading.

Automation worked normally for me previously.

Could you please check whether there is currently an issue with the Trello Automation/Butler service or with the powerup-loader.html iframe initialization?

I would appreciate confirmation whether this is a known bug and whether there is a workaround or fix.

2 answers

0 votes
Mike - Dreamsuite Consulting
Community Champion
August 28, 2026

Try this:

In Chrome dev console, go to Application > Storage. 
Click clear site data then refresh.

Screenshot 2026-08-28 161557.png

0 votes
Gabriela - LeanZero
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 27, 2026

Your console line is doing more work than the rest of the tests here. There was a Butler regression that produced this exact spinner and Atlassian rolled it back, but in those reports the network tab showed no failed requests at all, everything came back 200. You've got net::ERR_CONNECTION_RESET against app.butlerfortrello.com, and that's a different animal. Trello's status page is green as I write this too.

Butler is served from a separate host to the rest of Trello, and Atlassian's firewall doc lists it on its own line, telling you to configure host names to recognise any sub-domain of "*.trello.com *.trello.services *.trellostatus.com *.braintreegateway.com (paid accounts only) *.butlerfortrello.com". Anything that permits trello.com but resets butlerfortrello.com takes out the Automation editor and leaves the rest of Trello looking perfectly healthy, which is the shape of what you're describing.

The ping doesn't rule that out either. ICMP reaching the host says nothing about whether the TLS connection survives, and a reset lands after the packets are already flowing.

For the test that would actually split it: everything you varied, browsers, incognito, accounts, boards, even the hotspot, still ran through that one Windows machine. Anything inspecting HTTPS on the host follows it onto the hotspot. Try it from a different physical device.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events