Your JEDWare integration does not have the Call flow module yet. Open Admin settings takes you to the integration page; update it or ask your partner.
The JEDWare integration on your 3CX server did not answer. Check that its service is running, then Try again.
The Call flow module is not on your JEDWare licence, or it was removed. The page shows what the module does; Contact support to add it. If it disappears while you are working, the page shows “Licence not active” and returns to this state.
The integration could not reach the JEDWare licence service and has nothing cached, usually right after a restart without internet. Try again in a minute. This is not the same as being unlicensed.
Live publishing is not switched on for your account, or your partner pinned sandbox mode on the PBX. Hover the badge: it says “Live publishing follows the licence” or “Mode set in the integration settings”. See Who can use the Call Flow Designer. Testing in the sandbox works regardless.
“Dry run: publishing is disabled” means the PBX is pinned to review only. You can build, save and look at the change list, but not publish.
The integration is running but has lost its 3CX connection. You can edit and save, but not check or publish. Check the integration page under Admin settings.
Click it to jump to the first problem; the step with the problem carries a badge and the step settings explain it.
| Problem | Fix |
|---|---|
| A port still says Choose destination… | Connect every menu key, No key pressed, Wrong key and every opening-hours port, or pick Hang up. |
| The number is used by another flow | Remove it from one of the flows. |
| Prompt not found | Upload the WAV under Prompts. Names are case-sensitive on Linux PBXs. |
| A queue or ring group has no agents | Add at least one extension in the step settings. |
| Extension does not exist | Pick the extension from the list; it must exist on 3CX. |
| A menu key goes to an external number | 3CX cannot dial out straight from a menu key. Route via a queue or ring group. |
| “Smart steps are not available on this PBX” | Your 3CX does not support call scripts (older than V20 Update 5, or 3CX-hosted). Remove the step or use ordinary steps. |
Someone changed 3CX in between. The dialog shows the new change list; read it and publish again.
The row with the error names the object and the 3CX message. Typical causes: a number in the range is taken by a new extension, a prompt file was deleted, the PBX service restarted. Fix the cause, Publish… again. Your 3CX was put back as it was. “Some steps could not be undone. Check 3CX.” means the rollback itself hit an error; open the Admin Console and compare with the log (Copy log).
The undo would delete a menu or queue that another receptionist or another inbound rule still uses. Change that destination in the Admin Console, or add the object to a flow, then undo again. Nothing was changed.
The flow has no live publish standing, or “There is no backup to go back to”: it was never published live, or the copies were made by an integration without the undo feature. Set the number’s destination in the Admin Console.
runner.log for “prompt not found”.Open History…. If the last entry is a Test in sandbox, your number was never changed; run Publish live. If it is a live publish with the rule row marked OK, 3CX may have the old route cached for a few seconds; call again.
Open runner.log. Each key press is logged with its timing. If keys are missing, the trunk sends DTMF in a format 3CX does not detect; ask your provider for RFC 2833 / RFC 4733.
Opening-hours steps use the 3CX office hours of the department the destination belongs to. Check the department’s office hours in the Admin Console and its holiday list in Holiday Manager. A Close now override in Holiday Manager also wins over the schedule.
The script text was altered when pasting, usually a truncated paste. Download runner script again and paste the whole file. The compile message in the Admin Console shows the line.
<3CX data>\Ivr\Prompts\Callflows\<script name>\runner.log on Windows, /var/lib/3cxpbx/Instance1/Data/Ivr/Prompts/Callflows/<script name>/runner.log on Linux.