Why Do Rovo Connectors Show 0 Indexed Objects? [Champions Slack Insider]

[#1]

This thread turned into a full connector reality check fueled by @Susan Hauth _Jira Queen_ and @Yong Yang :

“I connected GitHub… but indexed objects = 0.”

Let’s walk through what’s actually happening—and what else surfaced along the way.

If your connector shows “0 indexed objects”

Start here: It’s usually not broken, it’s either early in the process or misconfigured.

Common causes:

• Timing: Indexing is not instant and can take several hours or longer depending on the connector and data volume.
• Permissions: Access must include specific repositories or projects, not just the organization. Private content must also be explicitly authorized.
• Connector state: Check Admin → Rovo → Connectors and confirm indexing is enabled and not paused.
• Recent changes: If permissions were updated recently, reconnect the integration to restart indexing.

If it still shows 0 after about 24 hours, it is likely a sync issue and worth opening a support ticket.

Will external tools create new objects in the Teamwork Graph?

Short Answer: No, external tools are mapped into existing Teamwork Graph object types rather than creating new ones.

Tools like GitHub or Asana are normalized into predefined structures such as tasks, comments, and users so Rovo can reason across systems consistently. Customers cannot define new object types at this time.

Connector capability varies more than expected

One important takeaway from this thread is that not all connectors behave the same way.

Zendesk example (current limitations)

Even when connected, data may sync but functionality is limited.

Results may appear in keyword search, but not in Rovo Chat, agents, or smart answers. This means you can retrieve items through search, but not use them effectively in conversational workflows.

Indexing limits and visibility

Limits exist per connector and are based on licensed user count, but Atlassian does not publish these limits in advance. You can view usage in Admin → Rovo → Connectors, where you’ll see indexed objects versus allowed capacity.

There are no overage charges today. If limits are reached, indexing simply stops until space is freed or limits increase.

Why indexing may stall

If indexing stops progressing, check whether you are near the object limit, whether permissions changed, or whether the connector is partially synced. If you are well below the limit and still stalled, it is most likely a sync issue rather than a capacity issue.

Champion takeaway

Rovo connectors are powerful but still evolving. Most issues fall into three categories: timing delays, permission gaps, or product limitations. Knowing which one you are dealing with can save a significant amount of time.

[Susan Hauth _Jira Queen_]

Thanks Valeri.  In addition, we can't search by the Zendesk ticket number in Rovo to return that Zendesk information.  I am in contact with Rovo Developers who are working on improving all of that!