Skip to content

Capsense exits after 72 hours when started by machine-level startup task due to Task Scheduler's execution limit #3

@MsRCAtN

Description

@MsRCAtN

--startup enable uses Task Scheduler for auto-start but does not explicitly set ExecutionTimeLimit, so the task inherits Windows' default runtime limit.

Microsoft documents that Task Scheduler stops a task 72 hours after it starts by default, unless ExecutionTimeLimit is changed; PT0S or Nothing allows the task to run indefinitely.

This can cause Capsense to exit silently after about 72 hours; if long-running background behavior is intended, set the limit to unlimited, otherwise provide an option or prompt to the user while set Task Scheduler for auto-start.

References:

https://learn.microsoft.com/en-us/windows/win32/taskschd/tasksettings-executiontimelimit
https://learn.microsoft.com/en-us/windows/win32/taskschd/taskschedulerschema-executiontimelimit-settingstype-element

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions