Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Trello integration failure


I do have implemented an integration using Google AppScript to automate card creation into a Trello board.


It was working fine with a daily batch sync, but for some unknown reason I've getting an error only when the code is called by the time trigger. As the error mentioned "BOARD_TOO_MANY_OPEN_CARDS" I've created a new one totally empty board but the error still persists. 


Worth to mention that if I run the code on the console cards are created regardless the number of opened cards it has.


Exception: Request failed for returned code 403. Truncated server response: {"message":"List has too many open cards","error":"BOARD_TOO_MANY_OPEN_CARDS"} (use muteHttpExceptions option to examine full response)


Thank you in advance,

1 answer

0 votes

Are you 100% sure the AppScript code is calling the board you think it is calling?  i.e. is it possible that the AppScript code that is throwing the error is hitting a different board?

Hi Michael, I’m pretty sure. First because it was working properly, the errors started couple weeks ago. Second, if I run the same code on the console it works fine. 

In other words, the exception is raisen only once the code is called by the time trigger.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events