Your workspace exists. You can sign in, your inboxes are there, your team can answer messages — and there is
no sign of your orders anywhere. This is the half-connected state, and it is the most common thing to go
wrong on the Store Syria path.

It is also the least alarming one. Nothing is broken and nothing was lost, because nothing had arrived yet.

## What you are looking at

Creating your workspace and connecting your store's data are **two separate requests**, not one. Store Syria
sends them one after the other, and the second is best-effort: if it is refused, the first is not undone.
The ordinary result is therefore a perfectly healthy workspace with no store data in it.

| What you see | What it means |
|---|---|
| Store Syria says the store is connected, but its **Store data** section is not | the workspace half finished and the store half did not |
| **Settings → Commerce** in Lynomia Chat lists no Store Syria store | the store half never reached your workspace |
| A conversation has no Commerce section at all | there is no connected store to read from |
| Store Syria offers **Continue setup** instead | the *workspace* half did not finish — start at [Set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria) |

The fix is almost never to start again. Pressing **Create workspace** again in the hope of a cleaner
workspace leaves you with a second workspace to look after and does nothing for the half that was refused.

## First, run the unfinished half again

1. In **Store Syria**, open **Communication & Marketing → Overview**.
2. In the **Store data** section, press the button it offers you: **Try again** after a refused attempt,
   **Complete store data setup** if it was never run, **Connect store data** if the sharing was stopped, or
   **Reconnect store data** if Lynomia Chat can no longer read the store. All four re-run the connection
   rather than reporting what Store Syria already knows, and none of them touches your workspace.
3. Read what it says next. Either the **Store data** section reads **Connected**, or you are given a
   reason — and every reason has its own answer below.

Running it again is safe. A store already connected with the same credential is left exactly as it is, so
you cannot end up with the same store twice. A store an administrator disabled in Lynomia Chat stays
disabled — that pause is your decision, not Store Syria's.

There is **no Verify button in Lynomia Chat**, and nothing here retries in the background. The next attempt
comes from the Store Syria side, and **Settings → Commerce** is where you read the result. Store Syria's
**Verify connection** is not it either: it appears only once the **Store data** section already reads
**Connected**, so it is a re-check of a working connection rather than a way to finish one.

![Working out why store data did not connect](media:commerce/store-syria-troubleshooting-en.png)

## What each refusal means, and what you can do

**Your plan does not include store data.** The workspace is created and the store half is refused on
purpose, so this is a billing question rather than a fault. Ask whoever sells you your plan; pressing
**Create workspace** again in the meantime changes nothing.

**The store is already connected to another workspace.** One store belongs to one Lynomia Chat workspace, and
a store that is spoken for is refused rather than quietly moved. You may see this as “This store is already
connected.” The usual cause is an earlier workspace nobody uses any more. An administrator of *that*
workspace disconnects the store under **Settings → Commerce**, after which this one is free to connect. If
you cannot work out which workspace holds it, Store Syria's support team is who to ask.

**There is no room left in your plan.** Every store your plan carries is in use, and **Settings → Commerce**
shows how many that is. Disconnect a store you no longer read, or raise the limit with whoever sells you
your plan. Disabled stores and stores needing re-authorization still hold their place; only disconnecting
frees one.

**The store rejected the credentials.** The credential reached your store and your store refused it, which
is reported as the store's refusal rather than a Lynomia Chat failure. On the ordinary path you pasted
nothing, so this one is Store Syria's to fix and their support team is the right first call. If your store
was instead set up by pasting an integration token, replace it under **Settings → Commerce → the store →
Replace keys**. That token comes from Store Syria's support and operations team rather than from your own
store admin, so ask them for a fresh one. A replacement is tested against the store before it is saved, so
one that does not work changes nothing.

**The store could not be reached just then.** A store that is slow, briefly down, or being asked too often in
quick succession produces a refusal that says nothing about your plan or your credentials. Wait a few minutes
and press **Try again** once more. Pressing it repeatedly makes this particular refusal more likely, not
less.

**The authorization was withdrawn.** If Store Syria tells you the authorization needs restoring, the store
half is not the problem — the permission that lets Store Syria act on your workspace at all is. No amount of
pressing **Create workspace** fixes that. Start at
[Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery).

## Confirm it is fixed

Do not judge this from Store Syria's page alone. Each side keeps its own record, and the one that decides
whether your orders are being read is yours.

1. Open **Settings → Commerce** in Lynomia Chat. Your Store Syria store is listed and **Active**, with the
   time it was last verified beside it. This is the real test.
2. Open a conversation with someone who has bought from you. The **Commerce** section names the store
   customer they were matched to and lists that customer's latest 5 orders.
3. After a plan or limit change, press **Try again** in Store Syria's **Store data** section once more. The
   store does not appear by itself.

One contact with an empty Commerce section is not a failure. Matching is exact, on a normalized email
address or a phone number in international form; names are never used, and guest checkouts match the same
way as registered customers. Connecting, disabling, replacing credentials and disconnecting are
**administrator** actions, each recorded in the audit log.

## When to contact support

Ask Store Syria first when the refusal is theirs to clear: a credential your store rejected, a store held by
a workspace you cannot find, or no Communication & Marketing section in your Store Syria menu at all.

It is worth a ticket once you have pressed **Try again** twice, several minutes apart, and been given the
same reason both times. Before that, a second attempt is faster. Tell them which store, by the name it
carries in Store Syria, roughly when it stopped working, and the reason you were shown, word for word.

**Never put a connection code, an integration token or a password in a ticket.** See
[raising a ticket with Lynomia](contact-lynomia-support) for how.

## Related

- [Set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria)
- [Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery)
- [Manage your Store Syria connection](store-syria-manage-the-connection)
- [Restore a Store Syria connection](store-syria-restore-the-connection)
- [What connecting a store gives you](commerce-overview)