Inside this article:

Packs are Coda’s version of plug-ins or integrations. They can help you consolidate your information and workflows across various platforms into Coda. But sometimes, you might run into an issue with your pack. Perhaps you’re getting an error message. Or maybe your Pack button, table, or formula just isn’t working as expected. Below, we discuss some common problems and how to troubleshoot them.

Looking to learn more about packs in general? Check out:

Reconnecting Pack accounts

Sometimes, you might run into issues with your Pack connection. Maybe you’re seeing an error message (”Failed to connect to [Pack Name]...”) or your table is refusing to resync. This can be caused by a number of issues, but it’s often resolved by the trusty “unplug and replug” troubleshooting step. So when in doubt, we often suggest the steps below:

“Sign in again”

Click Explore in the upper right of your doc, then select Packs & Import. Click into the pack that’s experiencing issues. You should then see a list of accounts that are connected to this pack. Go to the account that’s being used for the problematic formula, table, or button. If it’s a private account, you should see three horizontal dots next to the account name.

Screen Shot 2021-09-29 at 5.00.42 PM.png

If the account is a Shared account, click the down arrow next to the account name, and you should then see the same horizontal dots.

Screen Shot 2021-09-29 at 5.11.58 PM.png

Click those horizontal dots, then click “Sign in again.” Follow any prompts to re-authenticate that Pack account.

Once that’s done, try refreshing the pack via the Pack.

Screen Shot 2021-09-29 at 5.06.08 PM.png


If you’ve already tried to “Sign in again” following the steps above but the issue is persisting, you may need a harder refresh.

Head to and scroll down to “Accounts connected to Packs.” Find the particular pack in question. Click the down arrow next to the account name, and you should see a list of all docs where this Pack account is currently used. Find the problematic doc, and click the corresponding “Disconnect.”

Screen Shot 2021-09-30 at 12.57.44 PM.png

Then, back in the doc itself, you’ll need to reconnect to your account. You can connect it as a private account or shared account depending on your needs. See the Shared and private accounts for Packs section below for an explanation of these different account types.

How can I see which packs are installed in my doc?

First, open the doc. Then click on Explore in the upper right corner of your doc (note that your doc may say “Insert” or “Building Blocks” instead of “Explore”). Then select Packs & Import.

Screen Shot 2021-09-29 at 4.17.16 PM.png

Under INSTALLED, you’ll see all the Packs currently installed in your doc.

Screen Shot 2021-09-29 at 4.15.34 PM.png

Sync Table Settings

Why are some rows missing from my Pack sync table? Is there a limit for the number of rows in a Packs sync table?

If you’re missing some rows from your Pack sync table, this may be due to the row limit for the table. You can check this by clicking on the table Options at the upper right corner of the table. Then click on the first option (it’s usually the name of the Pack table).

Screen Shot 2021-09-29 at 4.21.28 PM.png

Click on Settings to expand the table settings. Here, you’ll see a TABLE LIMIT. You can set this limit to be 100, 1,000, or 10,000 rows.

Screen Shot 2021-09-29 at 4.21.41 PM.png

If your table was already at it’s limit, increasing the limit may solve the mystery of the missing rows (you’ll just need to resync the table after upping the limit).

Why is my Packs sync table not showing the most up-to-date information?

This may be due to the sync settings for the table. Following the instructions from the section above, open up the Settings for the Pack table.

Screen Shot 2021-09-29 at 4.27.32 PM.png

Here, you can adjust how often you’d like this Packs table to resync. If you choose “Manually,” you can resync your table as needed by clicking the blue 🔄 at the top of the table.

Screen Shot 2021-09-29 at 4.29.25 PM.png

Just be mindful that if your doc is particularly large or the table is particularly complex, choosing “Hourly” could slow down your doc.

Shared and private accounts for Packs

When to use a shared account vs. private account for Packs

Most Packs allow you to set up both private accounts and shared accounts. A private account is one that only you - the person setting up that account - can use to take actions from the Coda doc. A shared account is one that can be used to take actions by anyone who has access to the doc.

Screen Shot 2021-09-29 at 4.38.27 PM.png

For example, let’s say you have a button that sends Slack notifications. To set up this button, you have to select a Slack account that will be used to send those notifications.

One option is to select “User’s private Slack account.” This means that when anyone in the doc pushes this button, the Slack notification will be sent from their own private Slack account. If this person hasn’t yet connected their private Slack account to the Slack Pack in this doc, they’ll be prompted to do so when they push this button (read more about using the Slack Pack here).

Screen Shot 2021-09-29 at 4.42.32 PM.png

Alternatively, you could select Lena’s shared account as the account to use (note the two people icons indicate that this is a shared account). Then, when anyone in the doc pushes this button, it will send a notification from Lena’s Slack account - regardless of who is pushing the button.

To read more about setting up private and personal accounts with Packs, check out this article.

My automation is failing and I’m seeing an error that “Automation Bot does not have access to [Pack name]” - help!

Screen Shot 2021-09-29 at 4.32.51 PM.png

This issue is likely related to shared accounts (see the section above to understand the difference between private and shared accounts). If your automation is taking actions as Automation Bot, then you must make sure that the Pack action within the automation utilizes a shared account - not a private one. Only the account owner can use a private account to take actions via Coda; Automation Bot cannot.

You can resolve this by changing the automation action to use a shared account. Alternatively, you can change the automation to take actions as yourself rather than as Automation Bot. You can do this by clicking the option at the very bottom of your automation.

Screen Shot 2021-09-29 at 4.53.39 PM.png

Did this answer your question?