Erlangly releases

Erlangly 0.8.123

2026-10-14T00:00:00Z

Intraday: expected service level. Where there's no measured service level (your ACD or volume file doesn't say how many were answered within target), Intraday now shows the service level Erlang C expects from the contacts that came, their handle time and the agents on the phones, for lines planned with Erlang C.

Erlangly 0.8.122

2026-10-14T00:00:00Z

Intraday: where the hours went. A new Hours tab walks from the hours planned to the hours actually spent on the phones, step by step: less time away, exceptions and activities off the phone, less the time people weren't on the phones while scheduled on them, plus overtime and other time on the phones. What takes hours away is in red, what adds them in green.

Erlangly 0.8.121

2026-10-14T00:00:00Z

Intraday: adherence while scheduled on the phones. Intraday now shows how much of the time people were scheduled on the phones they were in adherence, and how much out, by interval, by day and over the range, beside the agents needed and on the phones. It counts from this release on: intervals scored before it show a dash.

Erlangly 0.8.120

2026-10-13T00:00:00Z

Intraday: Zoom Contact Center's service level. For a line of business connected to Zoom Contact Center, Erlangly now reads how many contacts were answered within each queue's own threshold, so Intraday shows its measured service level, and says when Zoom's threshold differs from the line's target. It needs one more optional permission on Zoom's side (contact_center:read:queue:admin); without it, contacts still come in as before.
Intraday fits the page. The Service tab's columns are grouped under Contacts, Handle time, Service level and Abandons, and both tabs fit beside the menu without scrolling sideways.

Erlangly 0.8.119

2026-10-13T00:00:00Z

Intraday: Amazon Connect's service level. For a line of business connected to Amazon Connect, Erlangly now reads how many contacts were answered and abandoned within the line's own service target, so Intraday shows its measured service level, and its short abandons where the target leaves them out. It needs no new permission in AWS.

Erlangly 0.8.118

2026-10-13T00:00:00Z

Intraday: Genesys Cloud's service level. For a line of business connected to Genesys Cloud, Erlangly now counts the contacts answered and abandoned within the line's own service target, so Intraday shows its measured service level, and its short abandons where the target leaves them out.

Erlangly 0.8.117

2026-10-13T00:00:00Z

Intraday: NICE CXone's service level. For a line of business connected to NICE CXone, Erlangly now also reads how long each contact waited in the queue, and counts it against the line's own service target, so Intraday shows its measured service level, and its short abandons where the target leaves them out.

Erlangly 0.8.116

2026-10-13T00:00:00Z

Intraday: Twilio Flex's service level. For a line of business connected to Twilio Flex, Erlangly now counts how long each call waited before it was answered or abandoned, against the line's own service target, so Intraday shows its measured service level, and its short abandons where the target leaves them out, without importing anything.

Erlangly 0.8.115

2026-10-13T00:00:00Z

Intraday: service level and answer rate. Where your ACD or your volume file says how many contacts were answered, and how many within target, Intraday's Service tab shows the answer rate and the measured service level against the target, in red where it's under. A line's service target can now be measured over the contacts offered, the contacts answered, or the contacts offered less short abandons (Settings → Lines of business → the line). Connected ACDs already send the contacts answered; answered within target follows, connector by connector.
The schedule by team. On a draft's day and week, choose a team beside Find and Sort to see only its people, with everyone's coverage and figures. A team lead's own team says "(my team)".
The API gives Intraday's times in local time with their offset, like every other endpoint, and takes contacts answered and answered within target with volumes.
What's new. The update note and Settings → System link to the release notes on erlangly.com, and an update that fixes a security problem says so, so you know to install it soon.
Licence notices. Each copy of Erlangly carries the licences of the open-source software it's built with (distribution/THIRD_PARTY_NOTICES.md), also at erlangly.com/third-party-notices.

Erlangly 0.8.114

2026-10-13T00:00:00Z

Supervisors can schedule coaching, training and meetings where there's overage. Planners turn it on for a line of business, with how many days ahead (3 unless changed): Settings → Lines of business → the line → Edit.
- Schedule an activity… on the schedule lets a supervisor choose the day, an activity off the phone (not breaks or lunch), how long, and who.
- Erlangly offers only the times when each person is on the phone, and the line keeps at least one agent more than it needs throughout.
- The activity goes on their shifts, and they're asked to look at their schedule again. Shift times, breaks and lunches stay as they are.

Erlangly 0.8.113

2026-10-13T00:00:00Z

Email and tickets: the first day of a forecast starts with the email already waiting. For a line planned to its response target within opening hours, the email that came in before the forecast starts, and isn't due yet, now counts as waiting when the line opens. Where it hasn't come in yet, the published forecast's figure counts instead. The first day's agents needed are now as even across the open hours as every other day's, instead of ramping up from nothing.

Erlangly 0.8.112

2026-10-13T00:00:00Z

Intraday: how the day went against the plan. A new Intraday page, for planners and supervisors, shows one line of business or all of them, for a day or up to 31 days.
- Service: the contacts forecast against the contacts that came, handle time and abandons.
- Staffing: the agents needed, scheduled and on the phones, and how busy they were.
- Each as a summary, then by day, by time of day across the days, and every interval.
- Agents on the phones come from your ACD's agent states. Erlangly fills in the states it already has, a day at a time, so earlier days appear over the next while. Service level comes next.
The guides, in planning order.
- Scheduling: set up shift patterns first.
- Forecasting and staffing: explains the two ways to get a forecast, made from your history or imported, with a new section on importing your volume history.

Erlangly 0.8.111

2026-10-13T00:00:00Z

Labour rules for four more countries. Signed rule packs for Belize, Trinidad and Tobago, Guyana and Barbados, each with its public holidays for 2026 to 2028:
- Belize: overtime past 9 hours a day or 45 a week, 9 hours' rest between shifts and an hour's break once the day runs over 6 hours (both stop a schedule being published), and at most 6 days in a row.
- Trinidad and Tobago: overtime past 8 hours a day or 40 a week and a 45-minute meal within the first 4½ hours, for agents paid up to 1.5 times the minimum wage (the law covers only them); a site or person can be given "Shift work" (a paid 20-minute break instead) or "Paid over 1.5 times the minimum wage" (the holidays alone).
- Guyana: overtime past 40 hours a week.
- Barbados: the holidays; a retailer's own contact centre can be given "Shops Act", with its hours, rest, days in a row and meal.
- Holidays proclaimed each year (Eid, Divali and Deepavali, Phagwah, Youman Nabi) come with the dates announced so far; add later ones with Add a holiday under Settings → Labour rules when they're announced, until an update brings them.
Settings → System doesn't fail when a database file goes while it's being measured.

Erlangly 0.8.110 (security fix)

2026-10-12T00:00:00Z

Admins hear about problems. When Settings → System says something needs looking at, each admin gets one email about it: not on every check while it lasts, and again only if it comes back after being put right for an hour. Nothing is sent until email is set up.
Email that couldn't be sent says who it was for. Settings → Email names the email and the address, and Settings → System names the last one for a day. Inviting many people at once no longer holds up other email: password resets, time-off answers and published schedules go first.
Adherence after a long silence. When an ACD connection that has sent nothing for 12 hours or more sends the states it kept, everyone on it is scored again for those intervals (a week back at most), not only the people the states are about. Importing or undoing a file of states does the same.
Big volume batches. A batch too big for the API (over 5,000 intervals or 2 MB) says how to split it: a week of one line of business at a time, with all its queues. The ACD and API guides show an example and the limits.
A licence ends at midnight on your clock. A key, a trial or a pay-once key's updates now end at midnight in your organisation's time zone, not UTC's, and Settings → Licence and its warnings count days the same way.
Sign-in. Signing in with SSO keeps the identity provider's details for an hour instead of fetching them each time (new signing keys are still picked up at once, and a test sign-in always reads them fresh). AI assistant apps can always register: at most 5,000 nobody has connected are kept, the oldest going first.
Security. Exports and import templates keep text that starts with = + - or @ as text, so a spreadsheet doesn't run it as a formula. Signing out, a password change or reset, or being made inactive ends that browser's live updates, and an expired session can't get them. Admins see a notice when Erlangly is used over plain HTTP at an address the internet can reach. The limit on password links can't be got round any more, and a sign-in form with a missing field says "Try another email address or password." instead of showing an error.
The erlangly command (from the next public release): a backup stopped partway leaves nothing behind and says so, and one killed outright is cleared by the next backup.
Release checks fail a release that takes more than 280 MiB of memory when idle.

Erlangly 0.8.109

2026-10-12T00:00:00Z

Less memory. Erlangly now runs its background work (jobs and the ACD connectors) in one process beside the web server instead of five, so it takes about 150 MiB less memory once started. Pages stay as fast while schedules are generated or adherence is scored, because that work still runs apart from the web server.
If the background process stops, Erlangly starts it again within seconds. A job cut short by a restart or an upgrade goes back in line and runs again; a job running when the background process failed is marked failed, and Settings → System lists it.
Release checks now also check that background jobs run after a restart, and measure memory the same way each time.

Erlangly 0.8.108 (security fix)

2026-10-12T00:00:00Z

Nobody changes their own time off. A supervisor or planner on the roster could change the dates or kind of their own approved time off on the Time off page, and it stayed approved. Changing it is deciding it again, so another supervisor now does it ("Change dates" shows only on other people's time off), and a time-off import no longer approves the importer's own.
Swaps show only what's on offer. Asking to swap for a shift that wasn't offered to you now says "Choose the shift you'd like in exchange", instead of saying whose shift it was. Accepting a swap asked of someone else answers "not found", as refusing one already did.
Fixes. Removing or changing a break that a labour rule needs shows the shift with the warning to acknowledge, instead of failing. Someone signed in who isn't on the roster is sent to My schedule when they acknowledge a schedule or answer a swap, instead of seeing an error.
Faster pages on a big floor. The week's schedule no longer slows down as time off piles up, and People, Time off, Exceptions and the week's adherence report show faster with hundreds of people.
Checked every time. Every page is now tried signed out and as each role to check that each role reaches only what it should, and the main pages are timed on a 500-person floor. Each release's check measures the image's size and the memory Erlangly uses once it has settled.

Erlangly 0.8.107

2026-10-12T00:00:00Z

Forecasts aren't thrown by outages. A time with no contacts on a day that otherwise has them, when the other weeks had contacts then, is left out of that week's part of the forecast instead of counting as zero, and the forecast says which times were left out. The hour the clocks skip in spring is left out the same way.
Leave days out of the history. On a line's volume history, you can leave out a day that wasn't normal (an outage, a spike, a one-off event) and put it back later; forecasts made after that use the history without it.
Repeated rows in a volume file count once. When two exports overlap, a row repeated for the same line of business, interval and queue is counted once instead of twice, and the preview says what it found.

Erlangly 0.8.106

2026-10-12T00:00:00Z

Adherence catches up. Each scoring run now also scores any intervals it missed (during a restart, say), and ACD states that arrive late are scored into the intervals they belong to. A state in a code nobody has mapped yet is kept and counted as unknown, rather than leaving the agent in their last state; once the code is mapped, those states are worked out again and the week is scored again. For the agent-state API, an unmapped code now answers unmapped and the state is kept (it was invalid, and refused).
Changes in the middle of a week. Generation now follows each day's lines of business, start date and contract: someone starting on a Wednesday gets shifts from Wednesday, someone moving from Billing to Tech on a Wednesday is planned on Tech from that day, and nobody gets shifts before they start or after they leave. A week that straddles two contracts is planned to their average by days.
Very busy queues. The agents needed on a queue with more than about 700 Erlangs in an interval were overstated by hundreds, and its service level showed as NaN. Erlang C now stays right at any volume, and an interval that would need more than 100,000 agents (in practice a typo) says so and asks you to check its contacts and handle time.

Erlangly 0.8.105

2026-10-12T00:00:00Z

After a restore, connections say what they need. On a server restored without the old one's key, an ACD connection whose secret can't be read now says "Enter the secret again" on its page and under Settings → System, instead of failing; entering it keeps the connection and its agent links. With Litestream on, erlangly.conf keeps a copy of the key, so a server restored from the copy reads every secret (keep the file as safe as your backups).
Monitoring. The guide now says how to watch Erlangly: an uptime check on /up, or /up?deep=1, which answers 503 while something needs looking at (no details shown); erlangly status from cron, which now exits with 1 while something needs looking at or Erlangly isn't up; disk space; and the clock.

Erlangly 0.8.104

2026-10-12T00:00:00Z

Everything in 0.8.103 (restarting and upgrading let work finish, a rollback asks first and keeps today's data, upgrades check for room, less disk), whose release check had a fault of its own: it said a rollback hadn't saved the data when it had. The check is fixed, and this release passes it.