Check status of indexed content

When you connect a third-party app to Teamwork Graph using a synced connector, Teamwork Graph indexes content from that app. This makes the content available in Rovo Search, Chat, and Agents for people who have permission to see it in the third-party app.

Use Check index status to confirm whether a specific file, document, or record is in the Teamwork Graph index. Paste a link to the item to see whether it's indexed and, when available, the date the indexed version was last modified.

This helps you investigate content someone expects to find but can't, validate a newly connected app, or check whether a recent change to your content has taken effect.

はじめる前に

• You need to have organization admin permissions in admin.atlassian.com. Learn about permissions

• The connector needs to be set up already. See Manage your Teamwork Graph connectors

• The index check is available for synced connectors. Direct connectors retrieve results live and don't store or index content with Atlassian, so there's nothing to check. See Teamwork Graph connector types

Check index status

1. admin.atlassian.com に移動します。複数の組織がある場合は、対象の組織を選択します。

2. Select Connectors, then open the connector that holds the content.

3. Go to the Check index status section.

4. Paste the link to the content you want to check. Use the link you'd normally copy from the third-party app — for example, the Copy link or Share link for a Google Drive file, or the address bar URL for a ServiceNow incident.

5. Select Check status.

The check is read-only. It doesn't start a sync, change any content, or change anyone's permissions.

Understand your result

What the last indexed modified date tells you

Alongside the indexed status, we show a last indexed modified date. This is the date the version we hold was last modified in the third-party app. It's the fastest way to tell whether the copy in your index is current or has fallen behind.

Compare it to when the content was last changed in the source app:

• If a Google Drive file was updated yesterday and the last indexed modified date is yesterday, you're holding the latest version, and Search results will reflect that update.

• If the same file was updated yesterday but the last indexed modified date is last week, you're holding an older version. Yesterday's change hasn't synced yet, so Search still returns the older content.

Things to know about your results

• Indexed isn't a guarantee of a search hit. Whether a specific person sees the content in Search depends on their permissions in the third-party app, plus the query, filters, and ranking. The index check tells you the content is available to be found — not that a particular search will surface it.

• Deletions follow the same sync cycle. Content you've just deleted or moved in the third-party app can still show as indexed until the next sync removes it.

Supported connectors and content types

You can check the content types listed below by pasting a link. We're adding support for more connectors and content types over time.

Content types not listed here may still be synced and searchable. They just can't be checked individually with this tool yet.

If content isn't indexed

A Not indexed result is expected in a few situations. Work through these in order:

1. Check the connector's status. On your connectors page, select the status icon for the connector. If it needs attention, content may not be syncing.

2. Give the sync time. Content that was created or changed recently, or a connector you've just set up, may not have synced yet. The first full sync after setup can take a while for large workspaces.

3. Check your content policy. Some connectors let an admin choose which content is indexed — for example, by allowing or blocking specific sites, or by setting time limits on how far back content is synced. Content that falls outside what you've chosen to include is deliberately excluded. Review the connector's setup guide for its content settings — for example, Choose content to include when connecting SharePoint and OneDrive.

4. Check the content type is one the connector syncs. Each connector syncs a specific set of content types. Anything outside that set won't be indexed. See the connector's own setup guide for what it covers.

5. Confirm the content still exists. If it was deleted, moved, or had its permissions changed in the third-party app, we may have removed it from the index — or be about to.

6. Check the link. Make sure you copied the link from the third-party app and that it points at the exact item, not a folder, search result, or preview.

If you've worked through all of these and content you expect to be indexed still isn't, contact Atlassian Support with the connector name and the link you checked.

Example link formats

These are the link formats we can read. If a check comes back with We couldn't resolve this URL, compare your link to the example for that connector — a link in a different shape is the most common cause.