claude-code - 💡(How to fix) Fix [BUG] Cowork — Failed to create scheduled task when Windows Documents folder is redirected to UNC path via Group Policy [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56001Fetched 2026-05-05 06:00:46
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Code Example

Failed to create scheduled task. You can try again.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Creating a scheduled task in Cowork always fails with the toast message "Failed to create scheduled task. You can try again." The issue is reproducible 100% of the time on machines where the Windows Documents folder is redirected to a UNC path via Group Policy (Folder Redirection). Colleagues on the same org/tenant whose Documents folder is NOT redirected can create scheduled tasks without any issues.

What Should Happen?

Scheduled task should be created

Error Messages/Logs

Failed to create scheduled task. You can try again.

Steps to Reproduce

Create a scheduled task in Cowork

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.123 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

No response

extent analysis

TL;DR

The issue is likely due to the Windows Documents folder being redirected to a UNC path, causing the scheduled task creation to fail, and a workaround may involve modifying the folder redirection policy or using a local folder.

Guidance

  • Verify that the issue is indeed caused by the folder redirection by testing scheduled task creation on a machine without the redirection policy applied.
  • Check the Group Policy settings to see if there are any specific restrictions or configurations that might be causing the issue.
  • Consider using a local folder instead of the redirected Documents folder to create the scheduled task, to see if this resolves the issue.
  • If possible, try temporarily disabling the folder redirection policy to see if scheduled task creation works as expected.

Notes

The exact cause of the issue is unclear, but it appears to be related to the folder redirection policy. Further investigation into the policy settings and the behavior of the Cowork application may be necessary to determine a permanent fix.

Recommendation

Apply workaround: Use a local folder instead of the redirected Documents folder to create the scheduled task, as this may allow the task to be created successfully while a more permanent solution is investigated.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork — Failed to create scheduled task when Windows Documents folder is redirected to UNC path via Group Policy [1 comments, 2 participants]