RStudio Session Recovery: Managing .RData Persistence During Workspace Transitions

Question

Workspace Image Recovery and Session State
RStudio manages session state by decoupling the IDE frontend from the R backend, utilizing a persistent session mechanism to restore open scripts and environment variables after a disconnect or crash. A core part of this behavior is the automatic loading of the .RData workspace image upon startup.
When transitioning between different RStudio Server versions or migrating to Posit Workbench, the interaction between the global environment persistence and the .Rprofile configuration can create conflicts. Specifically, there is a tension between the IDE's built-in session recovery and the manual control of environment state required for reproducible research.
If the "Restore .RData into workspace at startup" option is enabled in Global Options, it may override specific session initialization logic defined in the project-level configuration.

How does RStudio prioritize the .RData restoration sequence relative to the execution of a project-specific .Rprofile?
In what way does this priority change when moving from a standalone RStudio Server instance to a multi-session Posit Workbench environment?

Tasadduq Burney · Answer

Answer to the Core Questions
In both RStudio desktop/server and Posit Workbench the IDE follows the same two‑step startup order:

R loads the project‑level .Rprofile (executed in the same R session that will later receive the workspace image).
If the global option “Restore .RData into workspace at startup” is enabled, RStudio then loads the .RData file into that session.

Thus .Rprofile always runs first; any objects or options it creates are available to the subsequent .RData restoration.

Effect of Moving to Posit Workbench
Each Workbench session runs its own isolated R process. The two‑step order is preserved per session, but the .RData file is not automatically shared across users. A workspace image must be stored in a shared location and explicitly loaded in each session if you want cross‑session persistence.

Practical Verification Steps

Open Global Options → General and confirm whether Restore .RData into workspace at startup is checked.
Create a minimal .Rprofile in the project folder that prints a message and defines a test variable:

cat('Rprofile executed
')
x <- "from .Rprofile"

Create a .RData that contains a different value for the same variable:

x <- "from .RData"
save(x, file = ".RData")

Start a new session (desktop, server, or Workbench). Observe the console output and the value of x after startup.
In Workbench, repeat the test in a second session to confirm isolation.

What to Do If the Behavior Differs

Verify that the project folder is correctly set as the project root; otherwise .Rprofile may not be executed.
Check for a global .Rprofile.site or .Renviron that might override the order.
Ensure that the .RData file is not inadvertently shared across users unless that is intended.

Missing Diagnostic Detail
To tailor the recommendation precisely, could you confirm whether the Restore .RData into workspace at startup option is currently enabled for the project in question?

StepDescription

1Execute project‑level .Rprofile
2Load .RData if option enabled
3Session isolation in Workbench (each session independent)

RStudio Session Recovery: Managing .RData Persistence During Workspace Transitions

Workspace Image Recovery and Session State

1 answer

Answer to the Core Questions

Effect of Moving to Posit Workbench

Practical Verification Steps

What to Do If the Behavior Differs

Missing Diagnostic Detail

Your perspective belongs here.

0 question comments

Step	Description
1	Execute project‑level `.Rprofile`
2	Load `.RData` if option enabled
3	Session isolation in Workbench (each session independent)