Retry a failed integration action

This task concerns your native integrations such as Memberspot, Ghost or Meta Ads. Your invoices are not affected. On the dashboard and under Invoices in the "To review" tab it shows as "Review task", with a text that names the action. The task reminder by email, which is in German, lists it as "Zugang-Automatisierung fehlgeschlagen: Integration prüfen".

What happened

After a purchase or a refund, Rechnungskit uses the integration to grant access automatically, revoke it again or report a conversion event. If the other side is briefly unreachable, Rechnungskit tries up to six times at growing intervals, a good half hour in total. If the other side clearly rejects the action, for example because of an invalid key, there are no further attempts.

If the action fails for good, the task appears with one of these texts:

• "Access could not be granted automatically (…)" or "Access could not be revoked automatically (…)"
• "The conversion event could not be reported to …"

A typical cause is a changed or revoked key on the other side. If it rejects the key, that also shows on the integration's card. Ghost has one special case: if a member already has a paid Stripe subscription there, Rechnungskit cannot assign or remove a tier alongside it.

Why Rechnungskit stops here

Rechnungskit never revokes access because of an error and does not guess whether a customer should have access. If an action fails for good, the state in the third-party system stays as it was, and you decide.

How to resolve it

1. Open Connections → Integrations. Every grant and revocation is listed there in the integration's "Activity" log.
2. Check which action is marked "failed" and with which error.
3. Fix the cause, for example by saving a new key from the other side.
4. Click "Retry" on the action.
5. Check in the third-party system whether access is now correct. With Ghost, resolve a Stripe conflict directly in Ghost.
6. Mark the task as done under Invoices in the "To review" tab with "Mark as done".

When the task closes on its own

It does not close automatically. Even a successful retry does not close the task by itself. There is only one open task per failed action.

Related settings

• Connections → Integrations: connection, key and activity log per integration