Troubleshooting

Start at Settings → Integrations → Data sources. It shows every connection and when it last synced, which answers most questions before you go further.

The connection succeeded but no data arrived

Almost always scopes. A provider will happily issue a key that authenticates but can't read what you need.

The canonical case is a call source connected without transcript access: the connection validates, calls appear, and no transcripts sync. Each setup guide says which kinds of access the connection needs — check those against what you actually granted, at the provider.

Fix: re-issue the key or re-authorize with the right scopes, then reconnect.

Data is arriving but it's old

The last synced timestamp is the tell. A connection that last synced weeks ago is disconnected in every way that matters, even if the UI shows it as connected.

Look for a Reconnect prompt on the connection and use it. The usual causes:

• the token expired
• someone revoked Taizen's access at the provider
• the account that authorized it was deactivated (common after offboarding)
• a permissions change at the provider invalidated the grant

Agents produce generic output

Check sync before you rewrite the prompt. An agent with nothing specific to read produces generalities — that's not a prompt problem, and no amount of instruction tuning fixes it.

Order to check:

1. Is the integration synced recently?
2. Does the data you expect actually exist in the source? (Empty CRM fields are the second most common cause.)
3. Does the agent's scope include it? (what agents can see)

An agent can't write back

Write scopes weren't granted, or were narrowed later. A read-only connection reports the failure rather than silently skipping, so the run's steps will say so (runs and debugging).

Delivery fails but the run succeeded

There's a distinct run status for this: the work completed, posting it didn't. Usual causes:

• Slack: the app was removed from the channel, or the channel is private and Taizen isn't in it
• Email: the recipient address changed
• CRM: the key lost write access

The output isn't lost — it's on the run. Reconnect and re-run. See delivery.

It worked yesterday and fails today

Something changed at the provider, not in Taizen. Rotated keys, revoked OAuth grants, changed permissions, deactivated accounts. Check the provider's audit log if it has one.

First sync is taking a long time

Normal. The first sync backfills history. You can build and test agents while it runs; just be aware that an agent tested mid-backfill sees less data than it eventually will.

Nothing above matches

Two things worth doing before you ask for help:

1. Read one failing run end to end — inputs, steps, output. It usually names the problem (runs and debugging).
2. Note what changed. New integration, edited agent, rotated key, changed provider permissions. "It just started failing" almost always has a change behind it.

Then include the agent name, the run time, and the error from the run's steps when you report it.