Following the troubleshooting guide results in "unknown tenant at 0"

[douglasg14b]

My PAT didn't have a necessary scope, and the crawler needed to be reset so it would pull old data again.

I followed the troubleshooting guide to wipe crawler data, reset date, and delet ethe workspace.

# List indexes with:
docker-compose run --rm --no-deps api curl http://elastic:9200/_aliases?pretty=true
# Delete an index with
docker-compose run --rm --no-deps api curl -XDELETE http://elastic:9200/<index-name>


docker-compose run --rm --no-deps api monocle janitor wipe-crawler-data --elastic elastic:9200 --config /etc/monocle/config.yaml --workspace <workspace> --crawler-name <crawler-name>

docker-compose run --rm --no-deps api monocle janitor set-crawler-commit-date --elastic elastic:9200 --config /etc/monocle/config.yaml --workspace <workspace> --crawler-name <crawler-name> --commit-date 2023-01-01

After restarting the services, the UI just shows:

API request keep using an index that no longer exists, like the FE has a bad configuration.

After destroying the entire stack and recreating it, this persists. How/where do I clean up all state to reset it?

[douglasg14b]

Hm, after clearing everything by deleting and re-cloning, I realize now that the URL contains the workspace used.