Requesting portal hosting does not build your distribution while you wait. Rhythm builds it afterward in the background, and the hosting record is the only place to check its progress.
What Happens After You Save a Hosting Request
When you save a hosting record for the first time, Rhythm automatically starts building the web distribution behind it. You do not need to start anything separately, and there is no fixed amount of time it should take. Rhythm does not notify you when the build finishes, so check the hosting record later to see its status.
Tip
Hosting for a brand-new sandbox can require extra behind-the-scenes work before the portal is reachable. Do not expect a sandbox portal to respond immediately after you save the hosting request. Allow time for the distribution to finish building and for its domain name to start resolving before you test it.
A sandbox can also depend on earlier setup or change requests for your Rhythm account. If hosting takes longer than expected, earlier work may still need to finish before the portal becomes available.
Requesting portal hosting does not build your distribution while you wait. Rhythm builds it afterward in the background, and the hosting record shows how far that work has gotten.
What Happens After You Save a Hosting Request
As soon as you save a hosting record for the first time, Rhythm automatically starts building the underlying web distribution. You do not need to trigger anything separately, and there is no fixed amount of time you should expect it to take. Rhythm does not notify you when the build finishes, so check the hosting record later to confirm its status.
Tip
Hosting for a brand-new sandbox can involve extra behind-the-scenes work before the portal is actually reachable. Do not expect a sandbox portal to answer immediately after you save the hosting request. Allow time for the distribution to finish building and for its domain name to start resolving before you test it.
How Rhythm Records That Your Distribution Exists
When the distribution exists, Rhythm records that on the hosting record and includes an identifier for it. Rhythm writes this information shortly before the build fully finishes, so the record can show the distribution as built while the deployment is still wrapping up.
Asking for a Redeployment
Saving ordinary changes to your hosting record, such as adding a domain name or updating the certificate, does not rebuild the live distribution by itself. Rhythm records the change, but visitors will not reach the updated setup until you separately ask Rhythm to redeploy by changing the hosting record to request updated settings.
Every save you make while the record is in that state triggers another redeployment, even if nothing meaningful changed. Avoid saving repeatedly while you are still deciding on settings, because each save queues its own rebuild.
In some cases, Rhythm does not set up or redeploy a hosting record automatically, so it does not overwrite a distribution that was set up by hand outside the usual process. The article does not establish whether you can request this hold, or whether only Rhythm applies it. If you believe your hosting was built outside the normal flow, check with Rhythm Support before assuming an ordinary settings change will redeploy it.
Telling a Failed Build from One That Is Still Running
If a deployment fails, the hosting record does not show an error. It looks the same as a hosting request that is still being processed because there is no separate failed state.
The clearest sign that something did not complete is that the Console shows you the hosting request form again, but refuses the request when you resubmit it. If you see that pattern and hosting has been in progress longer than you would expect, contact Rhythm Support instead of continuing to retry the request yourself. The record alone cannot tell you whether the build failed.
Once the distribution exists, Rhythm records that fact directly on the hosting record, along with an identifier for it. Rhythm writes this slightly before the underlying build fully finishes, so there can be a short window where the record shows the distribution as built while the deployment behind it is still wrapping up.
Asking for a Redeployment
Saving ordinary changes to your hosting record, such as adding a domain name or updating the certificate, does not rebuild the live distribution by itself. Rhythm records the change, but visitors will not reach the updated setup until you separately ask Rhythm to redeploy by changing the hosting record to request updated settings.
Every save you make while the record is in that state triggers another redeployment, even if nothing meaningful changed. Avoid saving repeatedly while you are still deciding on settings, because each save queues its own rebuild.
In some cases, Rhythm holds off on setting up or redeploying a hosting record automatically, so it does not overwrite a distribution set up by hand outside the usual process. The article does not establish whether you can request this hold, or whether only Rhythm applies it. If you believe your hosting was built outside the normal flow, check with Rhythm Support before assuming an ordinary settings change will redeploy it.
Telling a Failed Build from One That Is Still Running
If a deployment fails, the hosting record does not show an error. It looks exactly like a hosting request that is still being processed because there is no separate failed state to distinguish the two.
The most reliable sign that something did not complete is that the Console shows you the hosting request form again, and resubmitting it is refused. If you see that pattern and hosting has been in progress longer than you would expect, contact Rhythm Support instead of continuing to retry the request yourself. The record alone cannot tell you whether the build actually failed.