Troubleshooting

Check your server.cfg load order — more_lib and more_dispatch must be ensured before more_dispatchapp. There's no database or SQL to import here; if it still won't register, check the F8 console for errors from more_dispatch or lb-phone failing to start.

Sending fails silently (the callback returns "error") in two cases: the faction isn't a key in MS.Jobs, or the reason field matched an entry in MS.BadWords. Check the F8 console with MS.Settings.dev_mode enabled — the client logs which check failed.

That's the per-player cooldown: after a successful send the app rejects further dispatches from the same player for MS.Settings.timeout seconds and shows the "timeout" locale message. This is tracked in memory (DispatchApp.Timeouts), so it resets on resource restart.

Each entry in MS.Jobs needs a matching "faction" key in more_dispatch's own MS.Jobs, or dispatches from that department will fail even though the card renders fine. Double-check both resources' config.lua use the same job name, and that "tag" and "desc" are filled in so the card doesn't look broken.

Set MS.Locale in config/config.lua to a key that exists in MS.Locales — only "en" ships by default in locale/en.lua. A raw key shown literally (e.g. "timeout") means GetLang couldn't find it in either the active locale or the "en" fallback; check that your locale file loaded and the key is spelled exactly as used in the script (currently just "title" and "timeout").