My supertagged nodes are not updating with the latest changes I'm making! What's going on?

Supertag template nodes are directly connected to the template until the moment you edit or make a change to them in the instance. Editing them in any way separates them from the template, and any change you make to the template will not reflect on edited template nodes. This is part of Tana Outliner's way to never destroy information you have touched and edited.

To refresh template nodes with the updated ones from the supertag template, consider first whether you have content you want to save, and move them out of the template element first. Then, perform a hard delete (Cmd/Ctrl + Shift + Backspace) to clear the stale node, and the template will immediately repopulate it.

I'm unable to delete nodes/fields in the supertag config, what's going on?

The tag might be extended, which means that it's inheriting fields from another tag. Check right above the supertag template to see if it has been extended.

Where is my imported content? The new workspace appears to be empty

Imported content is placed either under the new workspace's Library, or under the appropriate daily page depending on the contents of your import file.

For more on import, see Import data into Tana Outliner.

AI for Builders errors after activation

Errors when trying to run AI commands in Tana Outliner usually stem from one of two things:

Your OpenAI API key has not been entered
A payment method for using OpenAI's API has not been entered (this is a separate billing from ChatGPT, i.e. not included in a ChatGPT Pro subscription)

For more on how to set up OpenAI, read the AI for Builders documentation.

Fix "aiForBuilders feature not enabled" error

To activate AI for Builders, go to Settings, then Tana Outliner Labs, then AI for Builders.

It can happen that this setting gets reset if you switch browsers or client. This setting is stored per browser/client, not per account.

AI error messages: Out of budget and 0/1 left

You've got to understand that Tana Outliner uses the OpenAI API. This is a different product than the OpenAI chatbot ChatGPT. So even if you have a paid account with the OpenAI ChatGPT, this is of no use to using the OpenAI API.

You have a limited amount of free queries available with the OpenAI API. This is why you run into error messages after a week of using the AI facilities in Tana Outliner. So you've got to pay extra. The good news is that you can limit your credit to approximately $5 and you can limit your maximum spend per month.

How to get it working:

Enable AI in Tana Outliner (Settings, then Tana Outliner Labs, then AI for builders: check)
Login to platform.openai.com (not chat.openai.com)
Create a user account at platform.openai.com
Create a payment plan at the billing overview page. Register your credit card at payment method
Set usage limits on the limits page. This is where you can set a monthly budget
Get your API key from the API keys page
Go to Tana Outliner and paste your fresh API key in Settings, then API tokens (hit the Create button)
Reboot the app

"Retrying AI requests failed" error

This message means that the request to OpenAI was denied upon receipt, and there can be several reasons for this:

Not enough funds: Recently, OpenAI changed their payment rules and you have to prepay to cover for API costs
Token window too small: Your request may be spending too many tokens on the prompt. Switch model to one that has a higher token limit
OpenAI service disruption: If OpenAI's API is temporarily experiencing instability or down time, this may trigger this error. You can check their status at status.openai.com

Prompt variables not getting replaced

When building a prompt in a Command node, you're allowed to use variables that bring your data into the prompt. They look like this: ${name}

You are also allowed to use node references in the Prompt. However, if the contents of the reference has variables, they will not be replaced. Only variables written out in plain nodes will be replaced with your actual data.

"Editing in X places" yellow message

The "Editing in X places" message usually pops up for a moment when you are editing a node that is referenced in multiple places. It's a reminder that the changes you're making here reflect on X amount of other nodes in the graph.

To see all the other places this node is referenced, zoom into it and go to the Reference section at the bottom of the page. Here you'll find all the places in the graph where a reference of this node appears.

Checkbox node disappears when checked

This is likely because you have "Show completed items" unchecked. Open the user menu in the bottom of the sidebar, go to Settings, then Preferences, and check the "Show completed items" setting.

What does "Fields nested under other nodes" warning mean?

This warning pops up in the supertag template when there are fields that are indented (another word for nested). There are several "expected" behaviors of fields in supertags that only work when they are first-level nodes in the template, such as (and not limited by) the following:

Searching for nodes based on their field values (all #tasks with Status::Complete)
Viewing the node as a table, with fields as columns
Using fields to build title using title expressions

If you do not care for any of the above uses, you can safely ignore the warning.

Why is my field not auto-initializing?

There could be several reasons why a field isn't auto-initializing. Currently, field auto-initialization is triggered only on the event where a supertag is applied to a node, and the field is in a placeholder state (i.e. doesn't exist or have its own node ID).

Fields will therefore not auto-initialize under the following events:

When added anywhere as a solo field
On nodes where the supertag is already applied and the field is added after the fact
If the field is nested under a node in the supertag template. Fields have to be direct children to the supertag to auto-initialize

Can I trigger auto-initialization manually?

As a result of how initialization is triggered today, there is an unintentional quirk that can be used to re-initialize fields. For fields that fall under category 2 (from the list above), it is possible to trigger initialization by applying any supertag to the node. The fields have to be in a placeholder state, or it won't work.

Why can I not drag nodes between workspaces?

You may see error messages like "Cannot move notes between different shared areas" or "Cannot move nodes between different workspaces - use move command."

The reason for this message is that nodes are not made to easily move between workspaces. The workspace they belong to dictates a lot of things, such as permission to view and edit.

There are a couple of methods you can use to move nodes from one workspace to the other:

Option 1: Cut (Cmd/Ctrl+X) and Paste (Cmd/Ctrl+V) into new workspace
Option 2: Cmd/Ctrl+K, then "Move node to", then choose workspace and target (you can set custom targets in addition to the defaults of Today/Library/Home etc.)

Set [field] doesn't show all my fields, why?

The "Set [field]" command only works on field types Option, Instance, User and Checkbox.

Synced calendar events not getting tagged?

Tana Outliner performs an AI action to classify events coming in from your calendar. If an event doesn't match one of the classification profiles listed, AI is less likely to apply a tag to it.

To learn about the event classes currently supported, see the classification of events section in the Calendar integration documentation.

Help! I am not able to log into Tana Outliner

If you are not able to log into Tana Outliner, you can try to clear site data:

Open the Developer tools (Ctrl/Cmd+Shift+I) in the browser window.
Go to Application > Storage, then hit "Clear site data."

This will force-log you out of Tana Outliner. Restart the browser or desktop app, then try logging in again.