cci task run create_community (and sf community create) Appears to Loop/Timeout During Community Creation

[SankalpGhoshVera]

Describe the bug

Hello, I'm encountering an issue when attempting to create a new Salesforce Community using both the cci and sf commands. The process seems to get stuck in a loop where it times out, reports that community creation hasn't finished, and immediately retries, leading to a continuous cycle. The community is ultimately not created successfully.

Reproduction steps

CumulusCI Command:
cci task run create_community -o name "TestWebsite" -o template "Customer Service" -o url_path_prefix "testwebsite"

SF CLI Alternative:
sf community create --name "TestWebsite" --template-name "Customer Service" --url-path-prefix "testwebsite" --target-org alias

Your CumulusCI and Python versions

CumulusCI version: 4.6.0
Python Version :- 3.11

• Target Org Type: (Scratch Org)
• Community Template Used: Customer Service

Operating System

Windows 11

Windows environment

Command Prompt

CumulusCI installation method

pip

Error Gist

No response

Additional information

The log shows the following pattern: polling intervals increase until the 300-second limit, then a retry is initiated.

• Expected Behavior: The command should successfully create the Community and return a success message, or fail with a specific error indicating why the creation API call is taking longer than the allotted time.
• The issue seems to be with the API call hanging or taking longer than the default timeout for the Community creation process, specifically with the Customer Service template.

[dipakparmar]

@SankalpGhoshVera thanks for the report, can you confirm if you're able to create the site via SF CLI. We are not able to create either way, seems like only way works is from Setup UI.

[kg345]

Linking the reported issue in sf cli - we're also hitting the same thing and it's with Customer Service template
forcedotcom/cli#3419

[dipakparmar]

This issue is no longer happening. @SankalpGhoshVera, can you close this issue if you're no longer experiencing it? forcedotcom/cli#3419 (comment)