Messages and what to do
Lesson 24 of 25 7 min read
Every message the routing and module screens show, grouped by where you'll see it, with its cause and the right action.
The routing and module screens are precise in what they tell you. This lesson is a reference: find the message you're looking at, read why it appeared, and do the right thing. Keep it open while you work.
Anywhere
| Message | Cause | What to do |
|---|---|---|
| Saved. Takes effect within a minute. | The change is saved. | Nothing. Wait up to one minute. |
| That no longer exists. It may have been deleted elsewhere; refresh to see what is there now. | A different administrator changed or deleted the item. | Select Refresh. |
| A message that a delete is refused because something still uses the item | A route, type, module or group still uses it. | Remove the links that the message names, then try again. |
The screens don't update themselves
The screens don't update when a different administrator makes a change. Select Refresh, or open the page again, to see the latest values. Do this before any change you aren't sure about.
Adding an integration type
| Message | Cause | What to do |
|---|---|---|
| Routing 'message type': Service 'x' does not exist or is disabled. | When you added a type, a row named a service that is off. A different administrator may have switched it off after you opened the dialog. | Turn the service on, or choose a different service for that row. Then select Create again. |
| AS2 Service is switched off or does not handle Receive and Send, so the AS2 partner preset left those rows unticked. (an example of a preset note) | The preset's own service is off or can't do those message types. Presets never swap in a different service. | Find out why the service is off before you continue, or set the rows yourself. |
The Routing tab
| Message | Cause | What to do |
|---|---|---|
| Messages of Type are being discarded: the type supports them, but no service picks them up. | A supported message type has no service. | Choose a service on that row, or untick Supported. Do it now: messages are being lost. |
| Remove this type's module routes for Type first, on the Modules tab. | You tried to stop support while module routes use it. | Delete those routes on the Modules tab, then try again. |
The Routing Switches page
| Message | Cause | What to do |
|---|---|---|
| This service doesn't handle that message type. | You tried to turn on a link that doesn't exist. | Nothing. That service can't do that message type, as with AS2 and Create or Parse. |
The Set module dialog
| Message | Cause | What to do |
|---|---|---|
| A route for this combination exists already. Saving changes its module and switch. | You picked an organisation, document type and message type that already have a route. | If you meant to change it, carry on. If you meant to add a new route, check the organisation and document type. |
| Integration type 'x' does not support message type 'y'; add that routing support first. | You tried to add a module route for a message type that the type doesn't support. | Select Open the Routing tab. Tick Supported and choose a service. |
| Module 'x' serves message type 'y', not 'z'. | The module is for a different message type. | Select a module of the correct message type. |
The Modules page
| Message | Cause | What to do |
|---|---|---|
| A module with the key 'x' is catalogued already. Edit that one instead. | You tried to add a module with a key that's in the list already. | Edit the existing module. |
| Not found in the Integrations service (a warning on a row) | An enabled route names the module for a type routed to Integrations, but the service code has no module with that key. | Messages that need it fail. Tell a developer. |
The Module Groups pages
| Message | Cause | What to do |
|---|---|---|
| A group with the id 'x' exists already. Rename that one instead. | You tried to add a group with an id that's in use. | Use a different id, or rename the existing group. |
| Group 'x' routes message type 'y', which cannot be changed to 'z'; create a new group instead. | You can't change the message type of a group. | Add a new group. |
| Move it from group name? | The type is already in a different group for the same message type. | Select Move to swap groups, or Cancel to change nothing. |
Results and statuses worth knowing
- Not routedRouting tab: supported with no service. Messages are lost. Choose a service or untick Supported.
- OffRouting tab: a switch is off. Read the reason underneath.
- No route matchesModules tab Preview: no module route matches. Messages fail unless a published map or profile, or the code, selects a module. Normal for config-driven types.
- No module routesModules tab: the type has no routes. Correct for many types that use maps, profiles or coded modules.
Two administrators, one type
You and a colleague are both working on Acme SFTP. You try to edit a module route and see That no longer exists. It may have been deleted elsewhere; refresh to see what is there now. Your colleague deleted it a few minutes ago. You select Refresh, see the current routes, and agree with your colleague who will make the next change.
Recap
- Saved. Takes effect within a minute. is the normal confirmation.
- "Being discarded" on the Routing tab is an emergency: choose a service now.
- "Does not support message type" in Set module means fix routing first.
- "Not found in the Integrations service" means tell a developer.
- Ids, keys and group message types are permanent; the messages tell you to edit, rename or create instead.
- The screens don't refresh themselves. Select Refresh when in doubt.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.