Indexed
Guides

Keep Collections Up to Date

Update your indexed collections when source documents change.

Keep Collections Up to Date

Your source documents change over time — new Jira tickets, updated Confluence pages, new files added. Here's how to keep your search index current.

Update a Single Collection

Terminal
indexed index update my-docs
Updating collection 'my-docs'...
  Before: 24 documents, 96 chunks
  After:  28 documents, 112 chunks
✓ Collection 'my-docs' updated

This re-fetches documents from the original source, re-parses, re-chunks, and re-embeds them. For Jira and Confluence collections, it runs the same query you used when creating the collection.

Update All Collections

Terminal
indexed index update

This updates every collection in your index.

Re-index from Scratch

If you want a clean re-index (e.g., after changing configuration like chunk size), use --force when creating:

Terminal
indexed index create files -c my-docs -p ~/work/docs --force

The --force flag overwrites the existing collection entirely.

Automate with Cron

For collections that should always be fresh, set up a cron job:

Terminal
# Edit crontab
crontab -e
crontab
# Update all Indexed collections every day at 8am
0 8 * * * indexed index update 2>&1 >> ~/.indexed/update.log

PATH in cron

If indexed isn't found in cron, use the full path. Find it with which indexed.

What's Next