Troubleshooting
Working Days never guesses. If it cannot be certain of a date it stops the rule and tells you why, rather than writing a date that might be wrong.
Every message the app can show is listed here, with what causes it and how to fix it.
The code in brackets — for example WD-201 — appears in the automation audit log.
Still stuck? Open an issue or contact support.
Calendar and rule setup
The selected working calendar no longer exists
Code: WD-100
What you will see
Calendar '{calendarLabel}' no longer exists.
How to fix it
Someone deleted this calendar after the rule was built. Open the rule, edit the Working Days action, and pick a calendar that still exists — or recreate a calendar with the same working week and holidays.
No working calendar was selected
Code: WD-101
What you will see
No working calendar was selected for this action.
How to fix it
Edit the Working Days action in your rule and choose a calendar from the dropdown, then save the rule.
The calendar has no working days at all
Code: WD-102
What you will see
Calendar '{calendarLabel}' has no working weekdays, so no working day can ever be found.
How to fix it
Open Working Days in your app settings, edit this calendar, and tick at least one working weekday.
The calendar's time zone is not recognised
Code: WD-103
What you will see
'{timezone}' is not a recognised time zone.
How to fix it
Edit the calendar and choose a time zone from the list. Time zones use IANA names such as Europe/Oslo or America/New_York.
The calendar needs a name
Code: WD-104
What you will see
A calendar name is required.
How to fix it
Give the calendar a name you will recognise later, for example 'Norway Support' or 'UK Delivery'.
The calendar name is too long
Code: WD-105
What you will see
A calendar name can be at most {limit} characters.
How to fix it
Shorten the name. Calendar names appear in a dropdown inside the rule builder, so short names are easier to work with.
A non-working date could not be read
Code: WD-106
What you will see
'{value}' in the non-working dates list is not a valid date.
How to fix it
Non-working dates must be written one per line as year-month-day, for example 2026-12-25. Check the highlighted line for typos such as a missing digit or a day number that does not exist in that month.
A calendar with that name already exists
Code: WD-107
What you will see
A calendar named '{calendarLabel}' already exists.
How to fix it
Pick a different name. Two calendars with the same name are impossible to tell apart in the rule builder.
You have reached the calendar limit
Code: WD-108
What you will see
You can create at most {limit} calendars.
How to fix it
Delete a calendar you no longer use. If you genuinely need more, get in touch — we would like to hear what you are modelling.
Too many non-working dates in one calendar
Code: WD-109
What you will see
A calendar can hold at most {limit} non-working dates.
How to fix it
Remove dates from years you no longer need. Most teams only keep the current and next year.
Values coming into the action
The start date was empty
Code: WD-200
What you will see
startDate was empty.
How to fix it
The field you mapped into Start date produced nothing, so there is no date to work from. Either make sure that field has a value before this step runs, or — if you meant today — put {{now.jiraDate}} in the field. We stop rather than assume today, because assuming would quietly set the wrong deadline.
The start date could not be read as a date
Code: WD-201
What you will see
startDate could not be read as a date. Received: '{value}'. Expected {expected}.
How to fix it
If you mapped a smart value, add a date format to it — {{now.jiraDate}} rather than {{now}} — so it arrives as year-month-day. If instead you are typing dates in your own local style, such as 17/03/2026, open the Working Days action and set 'Date format' to match; we will not guess, because 03/04/2026 is two different days depending on where you sit.
That date is outside the supported range
Code: WD-202
What you will see
'{value}' is outside the supported range of {minYear} to {maxYear}.
How to fix it
Check the field you mapped in. A date far in the past or future usually means the wrong field was mapped, or a number was read as a year.
The number of working days was not a whole number
Code: WD-203
What you will see
offset must be a whole number. Received: '{value}'.
How to fix it
Enter a whole number of working days, such as 5 or -3. Half days are not supported. If you mapped a smart value, make sure it produces a number and not text.
That is more working days than we can move
Code: WD-204
What you will see
offset must be between -{limit} and {limit}. Received: {value}.
How to fix it
Use a smaller number of working days. Anything beyond this range is almost always a mapping mistake rather than a real deadline.
The adjustment setting was not recognised
Code: WD-205
What you will see
'{value}' is not a valid adjustment. Use none, nextWorkingDay or previousWorkingDay.
How to fix it
Edit the Working Days action and re-select the 'If the start date is not a working day' option, then save the rule.
The end date was empty
Code: WD-206
What you will see
endDate was empty.
How to fix it
The field you mapped into End date produced nothing, so there is no date to count to. Either make sure that field has a value before this step runs, or — if you meant today — put {{now.jiraDate}} in the field.
The end date could not be read as a date
Code: WD-207
What you will see
endDate could not be read as a date. Received: '{value}'. Expected {expected}.
How to fix it
If you mapped a smart value, add a date format to it so it arrives as year-month-day. If instead you are typing dates in your own local style, such as 17/03/2026, open the Working Days action and set 'Date format' to match; we will not guess, because 03/04/2026 is two different days depending on where you sit.
The date format setting was not recognised
Code: WD-209
What you will see
'{value}' is not a date format we know. Use iso, dayFirst or monthFirst.
How to fix it
Edit the Working Days action, re-select the 'Date format' option and save the rule. Leaving it unset means year-month-day, which is what Jira smart values already produce.
The calculation itself
That date is too far ahead for Jira to store correctly
Code: WD-208
What you will see
{value} is outside {minYear} to {maxYear}, the range Jira can store a date correctly.
How to fix it
Jira rewrites the century on dates outside this range, so a deadline in 2046 would silently be stored as 1946. We stop instead of letting that happen. Use a nearer date, or fewer working days. The range moves forward by one year every year.
No working day could be found
Code: WD-300
What you will see
Calendar '{calendarLabel}' has no working day within {searchLimit} days of {fromDate}.
How to fix it
This calendar marks so many days as non-working that no working day exists near this date. Open the calendar and check the working weekdays and the non-working dates list — a pasted range covering whole months is the usual cause.
Licensing
The app is not licensed on this site
Code: WD-400
What you will see
Working Days is not licensed on this site, so the calculation did not run.
How to fix it
Start a trial or buy a subscription from the Atlassian Marketplace listing, then re-run the rule. Rules stay configured while the licence is inactive — nothing is lost.
Problems on our side
Something went wrong inside the app
Code: WD-301
What you will see
An unexpected problem stopped the calculation.
How to fix it
This is a bug on our side, not a configuration mistake. Please report it on the issue tracker with the date, the number of working days and the calendar's working week — we do not receive your work item content, so we cannot see it from here.
Your calendars could not be loaded
Code: WD-500
What you will see
Your calendars could not be loaded right now.
How to fix it
This is usually a temporary platform problem. Re-run the rule in a few minutes. If it keeps happening, report it on the issue tracker with the time it occurred.
Getting help
We cannot see your work items, your comments or your descriptions — the app never receives them and never stores them. That means a bug report needs a little more from you than usual. The most useful report contains:
- the error code above,
- the calendar's working weekdays and its time zone,
- the start date and the number of working days you asked for,
- what you expected instead.