flowable/flowable-engine · error · org.flowable.common.engine.api.FlowableException

couldn't resolve duedate

Error message

couldn't resolve duedate: ${e.getMessage()}

What it means

Wrapper thrown by DueDateBusinessCalendar.resolveDuedate: parsing the configured duedate (ISO period/duration arithmetic) raised an exception; the underlying parse error message is appended. The duedate string does not conform to the expected date/period format.

Solutions

1. Fix the duedate to a valid ISO-8601 date, period or duration
2. Inspect the cause in the stack trace to see the exact parse failure

When it happens

Trigger: Thrown at modules/flowable-engine-common/src/main/java/org/flowable/common/engine/impl/calendar/DueDateBusinessCalendar.java:62 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of flowable/flowable-engine@d6d39ce1c6 (2026-09-11). Data as JSON: /api/errors/877339fc425506f1. Report an issue: GitHub.

Appendix: source

Thrown at modules/flowable-engine-common/src/main/java/org/flowable/common/engine/impl/calendar/DueDateBusinessCalendar.java:62

                    duration = Duration.parse(duedate);
                } else {
                    int timeIndex = duedate.indexOf('T');
                    if (timeIndex > 0) {
                        period = Period.parse(duedate.substring(0, timeIndex));
                        duration = Duration.parse("P" + duedate.substring(timeIndex));
                    } else {
                        period = Period.parse(duedate);
                        duration = Duration.ZERO;
                    }
                }

                return Date.from(calculateTime.plus(period).plus(duration).toInstant());
            }

            return DateUtil.parseDate(duedate);

        } catch (Exception e) {
            throw new FlowableException("couldn't resolve duedate: " + e.getMessage(), e);
        }
    }
}

View on GitHub (pinned to d6d39ce1c6)