Skip to main content

AssetPilot Connect activity, deliveries and sync runs

The Activity tab shows what AssetPilot Connect sent and synced. Use it to confirm deliveries and to recover from a receiver outage.

Pre-release

AssetPilot Connect is not on Atlassian Marketplace yet. It requires AssetPilot's app REST API, which is not in production. This page describes the release candidate.

Deliveries: two retrying after HTTP 500, the rest delivered.

Deliveries​

Each row is one attempt to deliver an event to a webhook, Slack channel or Teams channel.

ColumnShows
WhenTime of the delivery
Sent toThe target and its kind (Webhook, Slack, Microsoft Teams)
EventThe AssetPilot event, such as Checked out or Asset created
AssetThe asset tag
Attempt1 for the first try, up to 6 with retries
ResultDelivered, Retrying or Failed, with the HTTP status, duration, error and the time of the next attempt

Filter by Result and Sent to, or select Refresh. The list loads the latest deliveries first; the log keeps the last 500.

Redeliver​

After you fix a receiver, select Redeliver on the row. The result appears as a new attempt at the top of the list: Redelivered with the HTTP status, or Redelivery failed with the error.

Receivers should ignore duplicate X-AssetPilot-Delivery ids, so redelivering is safe. See Webhooks.

Sync runs​

The Sync runs sub-tab lists MDM runs from every source, with the same counts as the run log in each source's editor. It refreshes while a run is in progress.