WhatsApp Cloud API · error code

WhatsApp error 2593079: WABA already marked for migration to a different solution

Permanent - do not retryOnboarding, migration & partner setup

Last verified against Meta for Developers - Cloud API error codes

What WhatsApp returns
This WABA has already been marked for migration to a different solution ID

What error 2593079 means

Code 2593079 tells a partner that the WhatsApp Business Account is already queued to move to a different solution ID, so it cannot be marked again for your solution. It belongs to the On-Behalf-Of (OBO) ownership model, in which a solution partner owned the client's WABA.

That model is deprecated. Meta's deprecation notice set September 29, 2025 as the last day to onboard clients to OBO and October 1, 2025 as the last day to transfer ownership of OBO accounts to clients, with remaining eligible accounts auto-migrated in batches through the end of 2025. Partner-initiated account creation, in which the client owns the WABA, is the replacement. Meta's only listed resolution for 2593079 is to contact support.

If you are seeing this now, you are most likely running legacy partner code that still calls OBO-era endpoints.

Why it happens

  • Another partner or solution already initiated a migration for this WABA.
  • A second migration request from your own system after a first one was accepted.
  • Legacy OBO tooling still running after the model's deprecation.

How to fix WhatsApp error 2593079

  1. 1Check with the client which partner or solution the WABA is being moved to.
  2. 2Stop issuing further OBO migration calls for this account.
  3. 3Contact Meta support, as the error reference instructs, if the pending migration is wrong.
  4. 4Move new onboarding to the client-owned model described in Meta's OBO deprecation guide.

How to stop it recurring

Retire OBO-specific code paths entirely and onboard clients so they own their WABAs. Where legacy accounts remain, keep a ledger of which migrations you have requested so duplicate calls never leave your system. Search your codebase and scheduled jobs for OBO-era endpoints and remove them, so they cannot fire against client accounts by accident.

Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.

Related codes

Error 2593079 - quick answers

What does WhatsApp error 2593079 mean?

Code 2593079 tells a partner that the WhatsApp Business Account is already queued to move to a different solution ID, so it cannot be marked again for your solution. It belongs to the On-Behalf-Of (OBO) ownership model, in which a solution partner owned the client's WABA. That model is deprecated.

How do I fix WhatsApp error 2593079?

1. Check with the client which partner or solution the WABA is being moved to. 2. Stop issuing further OBO migration calls for this account. 3. Contact Meta support, as the error reference instructs, if the pending migration is wrong. 4. Move new onboarding to the client-owned model described in Meta's OBO deprecation guide.

Should I retry after error 2593079?

No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.

Stop debugging WhatsApp by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.