Share via

Project Online custom field update via Power Automate. Getting the error "CICOCheckedOutToOtherUser" but the users are the same

Anonymous
2025-06-20T20:33:58+00:00

Trying to update Project Online custom field via Power Automate.  Getting the error

PJClientCallableException: CICOCheckedOutToOtherUser\r\nCICOCheckedOutToOtherUser

We have a previous Action to Check Out the project so it should be the same resource ID checking the project in and doing the update. I have checked that both Actions use the same connector

When I look up the project in PO it shows the Checked Out To is the same ID that built and is running the flow

o

I look at the project in Project Center and it shows the same user as the one having the project checked out.

Anyone have any suggestions???

Microsoft 365 and Office | Project | Other | Other
Microsoft 365 and Office | Project | Other | Other

Microsoft project management software used to plan, manage, and communicate a project schedule and other information among workgroup members, project managers, and other stakeholders.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-06-21T00:21:03+00:00

    Hi Jaytu, 

    Thank you very much for your message and for providing detailed information about your flow and the error you are encountering. 

    From what you have described, it seems the issue is related specifically to Microsoft Power Automate when trying to update a Project Online custom field, despite the project being checked out to the same user running the flow. The error "CICOCheckedOutToOtherUser" typically indicates the project is checked out to another user, but since you have confirmed the same user is involved, this may be a subtle issue with how the checkout state is recognized by the API or connector. 

    Since Power Automate support falls under the Microsoft Power Platform area, and our current support scope focuses on Microsoft 365 products, I recommend posting your Answers forum, in the Microsoft Power Platform Community Forum Thread. This forum is actively monitored by experts and experienced users who specialize in Power Automate and Project Online integrations and can provide more targeted help. 

    When you post there, please include: 

    • A clear description of the issue
    • Screenshots of the error and your flow actions
    • The exact error message and any codes
    • Details about the connectors and actions used in your flow

    This will help the community and Microsoft engineers better understand the root cause and suggest possible workarounds or fixes. 

    I apologize for redirecting you, but this is to ensure you get the quickest and most accurate assistance possible. Thank you for your patience and understanding. 

    Please feel free to let me know how it goes or if you need any further assistance. If the solution I suggested doesn't work on your machine, just let me know. I’ll be here to check and provide more options.  

    If the information above is helpful, kindly mark it as an answer. This will also assist others in the community who may have similar questions complexity.  

    Warm regards, 

    Sophie N - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments