Activate a Site
/sites/management/api/v1/sites/{id}/activate
Bring a site online. A site must be offline and published before it can be activated.
Authorization
When site governance is enabled site administrators can activate any site. Any user that has been shared with a site and has one of the following sharing roles can also activate the site:
- Owner
- Manager
Activating Expired Sites
Expired sites cannot be activated. If a site has expired and there is a need to bring the site online then the site expiration date can be extended by the site manager.
For more information, see Extend the Expiration Period for a Site.
Path Alternative Identifiers
The default identifier for a Site resource is the Site Identifier. The Site resource supports alternative identifiers.
nameSite Name
Instead of the site identifier, the site name can be used to uniquely identify a site in the resource path. The default resource path parameter for a site is the site identifier, but when working with sites the human-readable site name is sometimes easier.
http://api.example.com/sites/management/api/v1/sites/name:MyNewProduct/activate
Introduced in release 19.4.1.
Redirection Response Examples
This operation responds with the following redirection (3xx) responses. For a full list of response HTTP status codes and example bodies, consult the Response section of this operation. Note: Depending on the client technology used to invoke this operation a 2xx response may be returned if the redirection is followed automatically.
303See Other - Successful Activation
When a site is successfully activated a see other response status code is returned and the Location
header contains the location of the activated site resource.
Client Error Response Examples
This operation responds with following client error (4xx) responses with exception details in the response body. For a full list of response HTTP status codes and example bodies, consult the Response section of this operation.
400Bad Request - Invalid Site Security Access
The security policy on the site means you cannot have the security access levels that have been specified. The security policy specifies the minimum level of security a site can have. For example, when the site security level in the security policy specifies service users, the security access cannot be all cloud users. You cannot publish a site or update site access members when the security access levels of the site are not allowed.
Error Code
OCE-SITEMGMT-009019
Resolution - Change Security Access
Change the site's security access levels to conform to the security policy of the site and retry the operation. When site governance is enabled you can specify security policy on a site by site basis, initially defined by the security policy on the site template that the site was created from. Any site that was created before site governance was enabled will not have a security policy on the site, so will fall back to tenant service level policy. If you get this error you can either set the security policy directly on that site to be public.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site on which the operation is being performed. |
For detailed information about this exception detail type, consult the InvalidSiteSecurityAccessExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Invalid Site Security Access", "status": "400", "detail": "Site security access levels are not allowed by the security policy.", "o:errorCode": "OCE-SITEMGMT-009019", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" } }
403Forbidden - Site Operation Forbidden
Your sharing role within the site does not allow you to perform the operation.
Error Code
OCE-SITEMGMT-009026
Resolution - Change the Sharing Role
Change the sharing role given to the authenticated user to the required role or higher.
Resolution - Change the Application Role
Ensure the user has a Standard User or Enterprise User Application Role.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site on which the operation is being performed. |
For detailed information about this exception detail type, consult the SiteOperationForbiddenExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Operation Forbidden", "status": "403", "detail": "You do have a sharing role in this site, but your role does not allow you to use this operation.", "o:errorCode": "OCE-SITEMGMT-009026", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" } }
Introduced in release 19.1.5.
403Forbidden - Storage Limit Reached
Storage transfer limit has been reached. Billing limits have been set on the amount of storage available by the system administrator.
Error Code
OCE-SITEMGMT-009098
Resolution - Increase Storage Limit
Get a system administrator to increase the storage limit.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
used | Storage used, in GB. |
limit | Storage limit, in GB. |
For detailed information about this exception detail type, consult the StorageLimitReachedExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Storage Limit Reached", "status": "403", "detail": "Storage limit has been reached.", "o:errorCode": "OCE-SITEMGMT-009098", "used": 1.23456789, "limit": 1.23456789 }
Introduced in release 20.3.1.
403Forbidden - Outbound Data Limit Reached
Outbound data limit has been reached. Limits have been set by the system administrator on the amount of outbound data.
Error Code
OCE-SITEMGMT-009100
Resolution - Increase Outbound Data Limit
Get a system administrator to increase the outbound data limit.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
used | Outbound data used, in GB. |
limit | Outbound data limit, in GB. |
For detailed information about this exception detail type, consult the OutboundDataLimitReachedExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Outbound Data Limit Reached", "status": "403", "detail": "Outbound data limit has been reached.", "o:errorCode": "OCE-SITEMGMT-009100", "used": 1.23456789, "limit": 1.23456789 }
Introduced in release 20.3.1.
404Not Found - Site Not Found
The site does not exist or has been deleted, or the authenticated user or client application does not have access to the site.
Error Code
OCE-SITEMGMT-009003
Resolution - Check Identifier
Check that the site identifier is valid.
Resolution - Check Membership
Check that the authenticated user is a member of the site or a site administrator.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site that does not exist or is not visible to the authenticated user. |
For detailed information about this exception detail type, consult the SiteNotFoundExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Not Found", "status": "404", "detail": "Site does not exist or has been deleted, or the authenticated user or client application does not have access to the site.", "o:errorCode": "OCE-SITEMGMT-009003", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" } }
409Conflict - Invalid Site Status
A site operation cannot be performed because the site is in the wrong state. An example attempting to bring a site online that is already online, or renaming an online site.
Error Code
OCE-SITEMGMT-009013
Resolution - Take Site Offline Before Updating Security Level
While a site is online, the site security level cannot be changed from a public to a secure site or vice versa. In order to change whether a site requires sign-in or not requires the site to be offline and unpublished.
Resolution - Take Site Offline Before Renaming
In order to rename a site it must be offline and unpublished.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site on which the operation is being performed. |
runtimeStatus | Site. Valid values are:
|
requiredStatus | Required site status. Valid values are:
|
For detailed information about this exception detail type, consult the InvalidSiteRuntimeStatusExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Invalid Site Status", "status": "409", "detail": "Operation cannot be performed on a site with status '{runtimeStatus}'.", "o:errorCode": "OCE-SITEMGMT-009013", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" }, "runtimeStatus": "offline", "requiredStatus": "offline" }
409Conflict - Invalid Site Publish Status
A site operation cannot be performed because the site is in the wrong publish state. An example is attempting to bring a site online that is unpublished, or renaming a published site.
Error Code
OCE-SITEMGMT-009031
Resolution - Unpublish Site Before Updating Security Level
While a site is published, the site security level cannot be changed from a public to a secure site or vice versa. In order to change whether a site requires sign-in or not requires the site to be offline and unpublished.
Resolution - Unpublish Site Before Renaming
In order to rename a site it must be offline and unpublished.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site on which the operation is being performed. |
publishStatus | Site publish status. Valid values are:
|
requiredStatus | Required site publish status. Valid values are:
|
For detailed information about this exception detail type, consult the InvalidSitePublishStatusExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Invalid Site Publish Status", "status": "409", "detail": "Operation cannot be performed on a site with publish status '{publishStatus}'.", "o:errorCode": "OCE-SITEMGMT-009031", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" }, "publishStatus": "unpublished", "requiredStatus": [ "unpublished" ] }
409Conflict - Site Deleted
The operation cannot be performed on a soft deleted site. This error can only occur when the includeDeleted
query parameter is set to true
.
Error Code
OCE-SITEMGMT-009059
Resolution - Restore Site
Restore the site and then try the operation again.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site that is soft deleted, if the site identifier has been provided. |
For detailed information about this exception detail type, consult the SiteDeletedExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Deleted", "status": "409", "detail": "The operation cannot be performed as the site has been soft deleted.", "o:errorCode": "OCE-SITEMGMT-009059", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" } }
Introduced in release 19.4.1.
409Conflict - Site Expired
The operation cannot be performed because the site has expired. For example, if a site has expired the site cannot be brought online.
Error Code
OCE-SITEMGMT-009069
Resolution - Extend the Site Expiration Period
Extend the site expiration period and retry the operation.
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site that has expired. |
expiration | Expiration date. Date and time values are in ISO 8601 yyyy-MM-dd'T'HH:mm:ss.SSS'Z' format using a UTC timezone. |
For detailed information about this exception detail type, consult the SiteExpiredExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Expired", "status": "409", "detail": "Operation cannot be performed as the site has expired.", "o:errorCode": "OCE-SITEMGMT-009069", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" }, "expiration": "2019-06-01T06:44:17.000Z" }
Introduced in release 19.4.1.
409Conflict - Site Activation Already In Progress
Can not request site publish/activation while it is currently being activated.
Error Code
OCE-SITEMGMT-009165
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Activation Already In Progress", "status": "409", "detail": "Unable to request site publish/activation while it is currently being activated.", "o:errorCode": "OCE-SITEMGMT-009165" }
409Conflict - Site Update In Progress
Can not request site publish/activation while it is currently being updated.
Error Code
OCE-SITEMGMT-009174
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site that has operation in progress. |
For detailed information about this exception detail type, consult the SiteUpdateInProgressExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Update In Progress", "status": "409", "detail": "Unable to request site publish/activation while it is currently being updated.", "o:errorCode": "OCE-SITEMGMT-009174", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" } }
409Conflict - Site Static Publish In Progress
Can not request site publish/activation while it is currently being static published.
Error Code
OCE-SITEMGMT-009175
Exception Detail Fields
This error type includes the following fields/values in the response:
Field Name | Description |
site | Site that has operation in progress. |
For detailed information about this exception detail type, consult the SiteStaticPublishInProgressExceptionDetail schema in the definitions section of the swagger document.
Example Response Body
{ "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1", "title": "Site Static Publish In Progress", "status": "409", "detail": "Unable to request site publish/activation while it has a static publish in progress.", "o:errorCode": "OCE-SITEMGMT-009175", "site": { "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0" } }
Request
-
id: string
Immutable identifier for the site.
-
includeDeleted(optional): boolean
Resources that have been marked for deletion can be read, modified, and support extended operations as long this query parameter is set to
true
. When theincludeDeleted
query parameter is not sent then the response to read, modification, and extended operations will be identical to that which would be returned if the resource was permanently deleted.
Response
303 Response
400 Response
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
object
InvalidSiteSecurityAccessExceptionDetail-allOf[1]
object
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
detail(optional):
string
Description specific to this occurrence of the problem. The human-readable, potentially multi-line details describing the problem in more details.
-
instance(optional):
string(uri)
URI to the link that provides more detail about the error.
-
o:errorCode(optional):
string
Application error code, which is different from HTTP error code. This code should be used to check for specific errors, rather than comparing fields such as the
title
ordetail
. -
o:errorDetails(optional):
array o:errorDetails
Multiple errors can be organized in a hierarchical structure.
-
o:errorPath(optional):
string
XPath or JSON path to indicate where the error occurs.
-
status(optional):
integer(int32)
Corresponding HTTP status code for the error.
-
title(optional):
string
Short, human-readable summary of the problem. It is not advisable to use the title as a way of checking for specific errors, use the
o:errorCode
for this purpose. -
type(optional):
string(uri)
Absolute URI that identifies the problem type. When this URI dereferenced, it should provide a human-readable summary of the problem, for example, as a HTML page.
object
-
site(optional):
string
Site on which the operation is being performed.
array
Multiple errors can be organized in a hierarchical structure.
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Invalid Site Security Access",
"status":"400",
"detail":"Site security access levels are not allowed by the security policy.",
"o:errorCode":"OCE-SITEMGMT-009019",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
}
}
401 Response
403 Response
-
allOf
SiteOperationForbiddenExceptionDetail
Introduced in release 19.1.5.
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
object
SiteOperationForbiddenExceptionDetail-allOf[1]
object
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
detail(optional):
string
Description specific to this occurrence of the problem. The human-readable, potentially multi-line details describing the problem in more details.
-
instance(optional):
string(uri)
URI to the link that provides more detail about the error.
-
o:errorCode(optional):
string
Application error code, which is different from HTTP error code. This code should be used to check for specific errors, rather than comparing fields such as the
title
ordetail
. -
o:errorDetails(optional):
array o:errorDetails
Multiple errors can be organized in a hierarchical structure.
-
o:errorPath(optional):
string
XPath or JSON path to indicate where the error occurs.
-
status(optional):
integer(int32)
Corresponding HTTP status code for the error.
-
title(optional):
string
Short, human-readable summary of the problem. It is not advisable to use the title as a way of checking for specific errors, use the
o:errorCode
for this purpose. -
type(optional):
string(uri)
Absolute URI that identifies the problem type. When this URI dereferenced, it should provide a human-readable summary of the problem, for example, as a HTML page.
object
-
site(optional):
string
Site on which the operation is being performed.
Introduced in release 19.1.5.
array
Multiple errors can be organized in a hierarchical structure.
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Operation Forbidden",
"status":"403",
"detail":"You do have a sharing role in this site, but your role does not allow you to use this operation.",
"o:errorCode":"OCE-SITEMGMT-009026",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
}
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Storage Limit Reached",
"status":"403",
"detail":"Storage limit has been reached.",
"o:errorCode":"OCE-SITEMGMT-009098",
"used":1.23456789,
"limit":1.23456789
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Outbound Data Limit Reached",
"status":"403",
"detail":"Outbound data limit has been reached.",
"o:errorCode":"OCE-SITEMGMT-009100",
"used":1.23456789,
"limit":1.23456789
}
404 Response
-
Cache-Control: string
Directives for caching mechanisms.
-
Content-Length: string
Size of the response body.
-
Content-Type: string
Content type of the response.
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
object
SiteNotFoundExceptionDetail-allOf[1]
object
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
detail(optional):
string
Description specific to this occurrence of the problem. The human-readable, potentially multi-line details describing the problem in more details.
-
instance(optional):
string(uri)
URI to the link that provides more detail about the error.
-
o:errorCode(optional):
string
Application error code, which is different from HTTP error code. This code should be used to check for specific errors, rather than comparing fields such as the
title
ordetail
. -
o:errorDetails(optional):
array o:errorDetails
Multiple errors can be organized in a hierarchical structure.
-
o:errorPath(optional):
string
XPath or JSON path to indicate where the error occurs.
-
status(optional):
integer(int32)
Corresponding HTTP status code for the error.
-
title(optional):
string
Short, human-readable summary of the problem. It is not advisable to use the title as a way of checking for specific errors, use the
o:errorCode
for this purpose. -
type(optional):
string(uri)
Absolute URI that identifies the problem type. When this URI dereferenced, it should provide a human-readable summary of the problem, for example, as a HTML page.
object
-
site(optional):
string
Site that does not exist or is not visible to the authenticated user.
array
Multiple errors can be organized in a hierarchical structure.
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Not Found",
"status":"404",
"detail":"Site does not exist or has been deleted, or the authenticated user or client application does not have access to the site.",
"o:errorCode":"OCE-SITEMGMT-009003",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
}
}
409 Response
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
object
InvalidSiteRuntimeStatusExceptionDetail-allOf[1]
object
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
-
detail(optional):
string
Description specific to this occurrence of the problem. The human-readable, potentially multi-line details describing the problem in more details.
-
instance(optional):
string(uri)
URI to the link that provides more detail about the error.
-
o:errorCode(optional):
string
Application error code, which is different from HTTP error code. This code should be used to check for specific errors, rather than comparing fields such as the
title
ordetail
. -
o:errorDetails(optional):
array o:errorDetails
Multiple errors can be organized in a hierarchical structure.
-
o:errorPath(optional):
string
XPath or JSON path to indicate where the error occurs.
-
status(optional):
integer(int32)
Corresponding HTTP status code for the error.
-
title(optional):
string
Short, human-readable summary of the problem. It is not advisable to use the title as a way of checking for specific errors, use the
o:errorCode
for this purpose. -
type(optional):
string(uri)
Absolute URI that identifies the problem type. When this URI dereferenced, it should provide a human-readable summary of the problem, for example, as a HTML page.
object
-
requiredStatus(optional):
string
Required site status.
Valid values are:
-
offline
- Site is offline. Site has not been activated, or was activated and was deactivated -
online
- Site is online. Site has been activated
-
-
runtimeStatus(optional):
string
Site.
Valid values are:
-
offline
- Site is offline. Site has not been activated, or was activated and was deactivated -
online
- Site is online. Site has been activated
-
-
site(optional):
string
Site on which the operation is being performed.
array
Multiple errors can be organized in a hierarchical structure.
-
object
ExceptionDetail
In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Invalid Site Status",
"status":"409",
"detail":"Operation cannot be performed on a site with status '{runtimeStatus}'.",
"o:errorCode":"OCE-SITEMGMT-009013",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
},
"runtimeStatus":"offline",
"requiredStatus":"offline"
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Invalid Site Publish Status",
"status":"409",
"detail":"Operation cannot be performed on a site with publish status '{publishStatus}'.",
"o:errorCode":"OCE-SITEMGMT-009031",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
},
"publishStatus":"unpublished",
"requiredStatus":[
"unpublished"
]
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Deleted",
"status":"409",
"detail":"The operation cannot be performed as the site has been soft deleted.",
"o:errorCode":"OCE-SITEMGMT-009059",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
}
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Expired",
"status":"409",
"detail":"Operation cannot be performed as the site has expired.",
"o:errorCode":"OCE-SITEMGMT-009069",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
},
"expiration":"2019-06-01T06:44:17.000Z"
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Activation Already In Progress",
"status":"409",
"detail":"Unable to request site publish/activation while it is currently being activated.",
"o:errorCode":"OCE-SITEMGMT-009165"
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Update In Progress",
"status":"409",
"detail":"Unable to request site publish/activation while it is currently being updated.",
"o:errorCode":"OCE-SITEMGMT-009174",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
}
}
{
"type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
"title":"Site Static Publish In Progress",
"status":"409",
"detail":"Unable to request site publish/activation while it has a static publish in progress.",
"o:errorCode":"OCE-SITEMGMT-009175",
"site":{
"id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
}
}