CopyProjectV4 - Action Faild. Project has scheduling in progress.

The error occurs because CopyProjectV4 validates that the target project is completely idle from a scheduling perspective before it allows the copy to proceed. If scheduling is still running or the project has had any prior activity, the action fails with the message that scheduling is in progress.

From the CopyProjectV4 behavior and validations:

1. The target project must be “new” and untouched
   • The action checks that:
     • The target project is new and has no previous activity, including simply opening the Tasks tab.
     • The project has not been copied before, no import was requested, and it does not have a Failed status.
   • Any of these conditions being violated will cause the copy to fail.
2. Why the “scheduling in progress” error appears intermittently
   • When a project is created, the scheduling engine may still be initializing or processing the schedule.
   • If CopyProjectV4 is called while that background scheduling is still running, the validation sees the project as “busy” and returns the error.
   • Because this is timing‑dependent, the same pattern can sometimes succeed and sometimes fail.
3. How to reduce or avoid the error in Power Automate In the flow that calls CopyProjectV4 after project creation:
   • Insert a delay before calling CopyProjectV4 (for example, a few minutes) to allow the scheduling engine to finish initializing the new project.
   • Ensure that no other automation, user, or integration opens or touches the project (especially the Tasks tab) before the copy runs.
   • Do not reuse a target project that has ever been used, copied, imported, or opened on the Tasks tab; always copy into a truly new project.
4. Monitoring / “good time of day”
   • The platform documentation does not expose a direct flag or API to query “scheduling in progress” for a project.
   • Instead, rely on:
     • Creating a fresh project and not touching it until CopyProjectV4 completes.
     • Adding a conservative delay in the automation before calling CopyProjectV4.
   • There is no documented “better” time of day; the key is ensuring the project is new and idle, not the clock time.
5. Additional behavior to be aware of
   • When a project is created via copy, the scheduling mode of the destination project always defaults to the organizational setting and cannot be changed at copy time. This is expected and not an error, but it is important when designing templates and automation.

In practice, the most reliable pattern is:

1. Create the project.
2. Wait a fixed delay in Power Automate (long enough for scheduling to complete under normal load).
3. Call CopyProjectV4 once, targeting that new, untouched project.
4. Ensure no user or process opens the project’s Tasks tab until after the copy succeeds.

References:

• Develop project templates with Copy Project
• Scheduling modes