Events
Utilise the Events page for a visual representation of the publishing and revalidation flow through Spark.
Once Spark has received a publish event from the source CMS platform, it will log events at each stage of processing through Spark.
The events page will serve up these events with a status to show the success/failure of each state of the process. In addition to a state, payloads can be viewed through the process and should any errors arise, these will be shown to assist with troubleshooting.
Clicking the payload, will show a modal detailing the payload at that stage of the process.
The process of the events is:
Received
The payload from the source CMS system has been received by Spark for processing. In this stage a success identifies that your company and environment association has been successful and the payload has been stored for the next stage, Processing.
The payload is the raw payload send from the source CMS system.
Processed
The payload is then picked up for processing, where it is mapped from its source schema into a generic schema structure used by Spark. If required, additional information is retrieved from the source system to provide additional context to the payload. Finally, the payload is batched and sent to the endpoints as per the configuration.
A "No Updates" status from the Processed state indicates that, after mapping, no updates were required to be sent to the application endpoints for processing. i.e. a media item publish. If there are no updates, the final Post Actions stage will no be run.
The payloads here are split by "outgoing" and "incoming".
- Outgoing payloads - detail what is sent to your application endpoint. A single payload will show for all endpoints configured.
- Incoming payloads - detail the response from your application endpoint, i.e. if the revalidation was a success. If there are multiple endpoints configured, the responses will be compiled into a single payload, and will contain duplicates of content (for each endpoint).
Post Actions
If processing is successful then the payload progresses to a Post Actions stage. This is where the updates are used to purge the Cloudflare cache or sent to a defined webhook endpoint.
Post Actions will also show an outgoing and incoming payload. For instance the outgoing payload to Cloudflare will detail the payload sent for cache purging, i.e. tag(s) or paths/URL's. Incoming payloads would signal a success/failure.
[SitecoreAI Only] SitecoreAI Webhook status
The Spark application automatically creates a publish end webhook in Sitecore's Experience Edge by default, when the setting "Allow Automated Updating Validation" is enabled.
The status of this webhook is displayed in right hand side of the Product Configuration page.
Should there be an issue in the webhook status, assuming the "Allow Automated Updating Validation" is ticked, it will be removed and re-added automatically.
Statuses that can be shown are:
Related to