Invite Conflict Resolution
Why Target Collab invites fail with "already invited" errors, and how Cruva's resolution options get your messages through.
The Short Answer
TikTok doesn't allow a creator to sit in multiple invites with overlapping products. If you're sending Target Collab invites for products A and B, any creator who is already in an invite containing product A or product B is in conflict — and TikTok will reject the new invite.
Resolution is Cruva's way around this: it moves the creator out of their old, conflicting invites and into the new one, so the message can succeed. When sending invites, you choose how aggressive that should be with three options: Resolve all creators, Resolve only creators who haven't accepted, or Don't resolve.
Why Conflicts Happen
Every Target Collab invite is tied to a set of products. TikTok enforces one rule across all of them: a creator can only be in one invite per product. The conflict check is per-product, so even partial overlap counts — if your new invite contains products A and B, a creator sitting in an old invite that contains just product A is still in conflict.
For active brands this comes up constantly. The creators you most want to invite are usually the ones you've invited before, which means they're already sitting in older invites for the same catalog. Without resolution, every one of those sends would fail.
The Three Resolution Options
Resolve all creators
Moves everyone out of their conflicting prior invites and into the new one — regardless of whether they accepted the old invite.
Two things worth knowing about creators who had already accepted:
- They don't need to accept again. The move carries their acceptance over, and the new invite simply bumps to the top of their inbox.
- If a move still fails because of a conflicting acceptance, you'll see "Creator accepted prior invite" in the activity logs for that attempt.
This is the maximum-deliverability option: as many messages get through as possible.
Resolve only creators who haven't accepted
Moves only the creators who never accepted their prior invite; anyone who has already accepted a conflicting invite is skipped.
An example: affiliate 1 sits in older invites containing products A and B but never accepted them; affiliate 2 sits in older invites where they accepted product A and/or B. With this option, affiliate 1 gets resolved and invited, while affiliate 2 is skipped entirely.
Choose this when you want to re-engage creators who ignored earlier invites without touching anyone who already has an active, accepted collaboration.
Don't resolve
Never moves anyone. Any creator who is already in a conflicting prior invite — accepted or not — simply fails, and the send moves on to the next creator. Failed attempts show "Creator already invited" in the activity logs.
This is the option for stores that never want to invite the same person twice. Be aware of the trade-off: if you keep inviting the same creators and they're all stuck in old invites, this setting leads to a lot of message failures.
When Resolution Still Fails (The Big-Invite Edge Case)
Occasionally you'll resolve and still see failures. The usual culprit is invite size.
When an invite contains a very large number of products (roughly 20+) and the target creators are each scattered across separate prior invites, the per-product conflict check produces a cartesian effect: thousands of individual invite moves have to be resolved just to send one batch. At that scale, TikTok's systems can reject the request outright.
When this happens, the activity logs will show "Creator already invited" even though resolution was on. It's a rare case, but if you're resolving and sends are still failing, an oversized product list is the most likely reason. Trimming the invite down to fewer products is the practical fix.
Reading the Activity Logs
The failure messages tell you which situation you're in:
- "Creator already invited" — the creator was in a conflicting prior invite and wasn't resolved. Either you chose Don't resolve, or you hit the big-invite edge case above.
- "Creator accepted prior invite" — the creator had already accepted a conflicting invite and the attempt failed on that acceptance (seen under Resolve all creators).
FAQ
If a creator already accepted an old invite and gets resolved into a new one, do they have to accept again? No — their acceptance carries over, and the new invite just moves to the top of their inbox.
Does resolution cancel the creator's old invite entirely? It moves the creator out of the conflicting invite so the new one can go through — the old invite no longer holds them for the overlapping products.
Which option should I default to? Resolve all creators, unless you have a specific reason not to. It delivers the most messages. Use "haven't accepted" when you don't want to disturb accepted collaborations, and "Don't resolve" only if your policy is to never invite the same creator twice.
I have resolution on but I'm still seeing "Creator already invited" — why? Almost certainly the big-invite edge case: too many products in one invite multiplied across creators in many separate prior invites. Reduce the product count and resend.
Was this article helpful?
Related articles
- How outreach automations workSet up DMs, invite cards, and email campaigns that target the right creators on autopilot.
- Find creators with AI SearchDescribe the creator you want in plain English, then add the matches to a list and launch outreach.
- Managing listsBuild and organize creator lists to group creators for outreach and keep your workflow organized.
- Email campaigns: setup, reconnecting, and deliverabilityConnect Gmail, Outlook, or a custom domain; fix 'Permission Issue'/reauth and 'no email found'; understand the 60/day limit and why your sent mail lands in Sent, not Inbox.
- Finding and managing creators (My Affiliates, AI Search, Lists & Groups)How to browse your affiliate roster, search for new creators with AI, upload creator lists, and build dynamic groups you can point an automation at.
- Creator L tiersWhat the L levels mean, exactly where the cutoffs sit, and how to filter for them anywhere in Cruva.