Waves

Waves is Coconut’s background execution system. It turns scheduled work and events into recorded tasks, runs those tasks when they’re due, and keeps their outcomes available for review. For publication monitoring, that means following a post beyond the request to publish it.

Follow the publication through to its outcome

Publication work has a destination, an admitted command, and a recorded outcome. Waves executes due work and handles follow-up when a provider result needs reconciliation. A request to publish is distinct from confirmation that the post is live.

Recheck the conditions before execution

The readiness gate checks the channel post’s content, media compatibility, connected account, and publishing authority. Scheduled work is checked again before execution, including the approval when one was required. These are publication requirements, rather than an editorial review of the post’s claims or tone.

Give each confirmed post a first-day monitoring schedule

For posts published through Coconut with a confirmed provider post identity, the Performance Wave schedules seven snapshots: 1, 2, 4, 8, 12, 18, and 24 hours after publication. The same schedule applies to each qualifying post.

A temporary capture failure can retry within the checkpoint’s capture window. If metrics remain unavailable, the checkpoint records that outcome. Metric availability depends on the connected channel and provider.

Bring the evidence into Inbox

After the capture window closes, Coconut produces a first-day performance report in Inbox. It includes the captured time series, identifies missing checkpoints, and retains the post’s subject and publication reference. A report can be complete, partial, or unavailable.

Where there is enough comparable history, the report benchmarks metrics against earlier posts of the same format on the same channel and brand. Those observations help you review the early response. They do not guarantee the post’s eventual performance.

Keep the follow-up independent of the browser

Waves stores task identity, due time, execution attempts, and outcomes in Coconut’s database. Workers claim due tasks and record their results. Monitoring continues without an open workspace tab, and failed or blocked work remains identifiable.