This page shows Stripe events received by ShopWrk. It does not show events you send to other services. If no events appear yet, the first will arrive when a customer pays an invoice or your Stripe account updates.
Reading the event log
Each row in the event log represents one Stripe event. The columns are:Event statuses
Succeeded
The event was received and processed without errors. No action is needed.
Pending
The event has been received but processing has not completed. This is normal briefly after an event arrives.
Failed
Processing encountered an error. The error message is shown below the status badge. The event persists in the log so it can be replayed after the cause is fixed.
Replaying a failed event
If an event fails — for example, because of a temporary network issue or a misconfigured integration — you can replay it once you have resolved the underlying cause.1
Find the failed event
Look for any row with a Failed status badge. The error message below the badge describes what went wrong.
2
Resolve the cause
Fix whatever caused the failure before replaying. For example, if the failure was due to a past-due payment, update the payment method first.
3
Click Replay
Click the Replay button on the failed event row. A confirmation dialog appears describing the event and warning about side effects.
4
Confirm the replay
Click Replay event in the confirmation dialog. ShopWrk re-fetches the event from Stripe and runs the handler again. A success or error message appears when the replay completes.
The Replay button is only available to users with the Owner role. Admins see an “Owner only” indicator instead.
When to use replay
Replay is useful when:- A payment event failed due to a temporary error and the payment itself actually succeeded in Stripe
- A subscription update did not apply because of a processing error
- You updated a misconfigured integration and need the event to re-run
