Audit Unpublished Content on RStudio Connect#
Answer the Question:
- How many content items have been left in an unpublished state on the server?
This report runs an audit of content items on your RStudio Connect server with an "unknown"
app_mode. A content item can end up in this state when it fails to deploy. Content items that were last deployed over thirty days ago and remain unknown should likely be cleaned up (removed).
Step 1 - Get the report code#
Step 2 - Run & Customize the report#
This R Markdown report uses the
/v1/content API endpoint available in RStudio Connect 1.8.6 and later. Visit the RStudio Connect API Reference documentation for more information.
Requirements: Administrator API Key
.Renviron file to store your API key and RStudio Connect server URL.
Your RStudio Connect server URL is the same URL you use to access the RStudio Connect dashboard, minus the connect path. If you access the dashboard at
https://rsc.company.com/connect/, the server URL is
# ~/.Renviron # The CONNECT_SERVER URL must have a trailing slash. CONNECT_SERVER="https://rsc.company.com/" CONNECT_API_KEY="mysupersecretapikey"
Restart your R session to pick up on the new environment variables.
Step 3 - Publish the report to RStudio Connect#
If you are push-button publishing from the RStudio IDE, we recommend the selection "Publish document with source code" so that the report can be re-executed on a schedule.
Source code documents that use
Sys.getenv() to load the server URL and API Key will fail to complete the
knit process on first deployment.
To fix the failed
- Navigate to your incomplete content item on RStudio Connect.
- Open the
Varscontent management pane.
- Add your
- Re-execute the content code by clicking on the "Refresh Report" button (shown below).
Step 4 (optional) - Set the report to update on a schedule#
Automate a data refresh of your report by setting it up to run on a schedule. Open the
Schedule content management pane to get started.
Read more about Scheduling in the RStudio Connect User Guide.