Store Syria has stopped reporting a healthy connection to Lynomia Chat. Its Lynomia Chat page offers to connect again instead of showing a connection, the shortcut that used to sign you straight in no longer does, and anything Store Syria tries on your behalf comes back refused.
Read the reassuring part first. Nothing was deleted, nothing is corrupted, and your team can carry on working. One permission was withdrawn. One action puts it back, and only someone inside your workspace can take it.
What you are looking at
| What you see | What it means |
|---|---|
| Store Syria says the authorization needs restoring | the permission that lets it open your workspace has been withdrawn |
| Store Syria's Lynomia Chat page offers to connect again | the same fact, in the place you normally read |
| The Store Syria shortcut shows the ordinary sign-in failure | it had no authorization to sign you in with |
| Continue setup or Verify in Store Syria is refused | every request Store Syria makes on your behalf is refused |
| Connect an external platform reads “This connection was ended. Generate a new code to connect again.” | the Lynomia Chat side of the same fact |
Trust the last row, because it is written on your own side. Sign in to Lynomia Chat normally and open Settings → Integrations → Connect an external platform to read it.
Where the authorization went
Almost always somebody in your own workspace ended it, and meant to at the time.
That same screen lists every platform that can currently open this workspace, under Connected platforms. Each entry carries a Disconnect button, and the confirmation says plainly that the platform will lose access immediately and anyone signed in through it will be signed out. Store Syria is one of those entries. Press it and Store Syria keeps nothing — from that moment every request it makes against your workspace is refused, which is the notice you are now reading on its side.
It is an administrator action and it is recorded in the audit log, so who did it and when is answerable rather than a mystery. The reasons are usually ordinary — a tidy-up by somebody who did not recognise the entry, a trial connection cleared away, an access review after an administrator left — and the way back is the same for all of them.
Nothing was deleted
Worth stating item by item, because the notice reads more alarming than the situation is.
- Your workspace is intact. It was not closed, suspended or replaced.
- Every contact is intact, with its attributes and its labels.
- Every conversation and message is intact — from before the authorization was withdrawn and from during it. Your team can keep answering customers throughout.
- Your inboxes, your agents and their roles, your automations and your reports are untouched.
- Nothing in Store Syria changed. No order, no customer and no setting of yours was altered there.
Signing in the ordinary way still works: the sign-in page, your email address, your password. The Store Syria shortcut is a convenience, not the only door. If you have never set a password, because your workspace was created for you, use Forgot your password? there.
What is actually blocked
What was withdrawn is narrower than it looks, and knowing its edges saves a wasted hour.
Store Syria cannot open your workspace at all while this lasts. It cannot sign you in through the shortcut, cannot report on the connection, and cannot set up, finish or re-run store data for you. A store setup that never finished stays unfinished until this is restored, and pressing Continue setup or Verify in Store Syria will not get past it.
Your store data is the other half of the arrangement and answers its own question. Settings → Commerce is where you read whether your Store Syria store is listed and Active, with the time it was last verified beside it — and you reach that screen by signing in normally, so the withdrawn authorization does not stand between you and the answer.
Restoring the authorization is therefore not a store repair. If no Store Syria store is listed, the store half never arrived: Store Syria store data did not connect is where to finish it. If it is listed but not Active, manage your Store Syria connection explains each state.
How to put it back
One action: generate a fresh connection code in Lynomia Chat and let Store Syria use it. The steps, the rules the code lives by, and how to confirm it worked are in restore a Store Syria connection, so they are not repeated here.
Three things are worth knowing before you open it.
- You have to do it yourself. Neither Lynomia support nor Store Syria can generate the code for you — producing one is what proves you control this workspace. You need the administrator role.
- It reconnects the workspace you already have. It does not create a second one, and trying again after a refused attempt is safe.
- Never send the connection code to anyone — not by message, not by email, not to support. Anyone holding it can connect a platform to your workspace. It is shown once and lives one hour. You paste it into the Lynomia Chat page inside Store Syria yourself.
Nothing restores this on a schedule. Lynomia Chat does not sweep for withdrawn authorizations in the background, so the connection waits until an administrator generates that code.
If Store Syria set your workspace up
A workspace that Store Syria created and manages has no Disconnect button on its entry under Connected platforms — in its place is a sentence saying Store Syria manages the connection and that it should be ended from Store Syria instead. That absence is deliberate: ending a managed authorization from this side alone would strip the access the whole arrangement rests on.
So if a managed workspace is showing this notice, it is unlikely anyone on your team caused it. A fresh code is still worth one attempt; if that does not clear it, ask Store Syria's support team rather than repeating it.
Related
- Restore a Store Syria connection
- Manage your Store Syria connection
- Store Syria store data did not connect
- What the Store Syria integration gives you
- What connecting a store gives you
If it does not work
I am not an administrator. Then you cannot restore it, and nobody outside the workspace can do it for you. Ask an administrator to work through restore a Store Syria connection.
I generated a code and the notice is still there. The code may have expired, been used already, or been mistyped — all three are answered the same way, so the message will not say which. A refused attempt uses the code up, so generate a fresh one rather than retrying the old one, and let Store Syria use it straight away.
Store Syria will not let me end the connection from its side. That is consistent: with the authorization withdrawn, Store Syria cannot act on your workspace, and ending the connection is an action. Restore it first, then end it from Store Syria if that is still what you want.
The authorization is back and there are still no orders beside conversations. The two halves are separate and you have fixed one. Work through Store Syria store data did not connect.
It keeps happening. Generating codes forever is not the answer. Check who holds the administrator role, and that nobody is clearing the entry under Connected platforms as routine housekeeping.
It is still not resolved. Raise a ticket once two consecutive fresh codes have been refused. Say which store, by the name it carries in Store Syria, and roughly when it stopped working. Never include a connection code, a password, or a screenshot showing either — see raising a ticket with Lynomia.