Short Answer: Those messages appear when no documentation has been generated or when no runs exist for the selected repo/filters; connect repos and run documentation or remove filters.
Answer
PreRequisites
-
Access to the CodeDoc workspace
-
Connected repository (if expecting results)
Steps
-
Open the Documentation and Usage tabs to confirm the empty-state message.
You see either "Your documentation is empty" (Documentation) or "No documentation runs yet" (Usage). -
Check that repositories are connected to CodeDoc (Overview empty-state messaging indicates this) and that you have permission to run documentation.
You confirm whether a connection or permission is missing. -
If no runs exist, click "Generate documentation" or set up an Automation to create runs.
A documentation run is created and will appear in Usage when complete. -
If results still do not appear, clear any filters (Repository, Date, Search) on the Usage/Documentation pages and refresh the page.
Any hidden results should appear if they match the cleared filter criteria.
Troubleshooting
-
I ran documentation but still see the empty state.
LikelyCause: Run may have targeted a different branch, is still processing, or failed.
Action: Open Usage to confirm the run status and which branch/repository it targeted; rerun if necessary. -
Repositories should be present but are not listed.
LikelyCause: Repository integration was not completed or required permissions not granted.
Action: Reconnect the repository integration and ensure the app has permission to read the repository.
Note: Empty-state text provides the next step (e.g., connect repository or run documentation); follow that guidance first.