为何ViewActivation.prepare中task.started未执行保存？是特性还是Bug？

Great question—this is a nuanced detail in Viewflow's activation lifecycle that ties directly to performance optimization, so let's break it down.

First, let's recap your observation: you've noticed other activation classes (like ManualActivation or AutoActivation) immediately call self.task.save() after setting self.task.started = now(), but ViewActivation.prepare() skips this explicit save.

This is almost certainly a deliberate design choice, not a bug, and here's why: #

• Transaction-bound lifecycle: ViewActivation is tightly coupled to web view requests, which often run within a database transaction wrapping the entire view processing. The prepare() method runs early in the view flow, and there may be additional modifications to the task (like status updates, owner assignments, etc.) later in the same request. By deferring the save until the transaction ends, Viewflow avoids multiple unnecessary database round-trips—this is a standard optimization to cut down on IO overhead.
• Lazy saving pattern: Viewflow uses a "lazy" approach to task saving in contexts where multiple changes are expected. Instead of saving on every attribute update, it relies on the transaction commit (or a later explicit save in the activation workflow) to persist all changes at once. For ViewActivation, the save is likely handled in a downstream method like activate() or when the view request completes and the transaction is finalized.
• Context-specific behavior: Unlike other activation types that might trigger asynchronously or in isolation (e.g., auto-activated nodes running in background tasks), ViewActivation operates within a user-initiated web request. The request's transaction boundary provides a natural point to batch-save all changes, which aligns with web app performance best practices.

For your performance analysis tool: #

If you're relying on the started timestamp being immediately visible in the database, you'll need to account for this deferral. The timestamp is set in memory right away, but it won't persist to the database until the transaction commits. You might want to hook into Viewflow's post-commit signals, or check the task's in-memory state instead of querying the database directly during view processing.

内容的提问来源于stack exchange，提问作者Tinker