# Dapr v1.17.11

2026-07-17 · [Original release notes](https://github.com/dapr/dapr/releases/tag/v1.17.11) · [Full summary](https://ratatosk.io/en/releases/dapr/v1.17.11)

Important fixes 2 · Other changes 2

## Important fixes (2)

### Correct metadata in actor reminder listings

- Affects: actors with IDs containing `||`

> Listing reminders for actors whose IDs contain `||` now also reports the correct actor metadata.

### Scheduler accepts Dapr-valid reminder names, job names, and actor IDs

- Affects: Scheduler-backed actor reminders and scheduled jobs

Previously, reminder registration failed when a reminder name or actor ID contained characters such as `|` or `@`, and scheduled job names outside the strict DNS-1123 set were also affected. Names and actor IDs now allow uppercase letters, `|`, `@`, and `||`; `/`, `\`, `#`, `?`, control characters, and the exact path sequences `.` and `..` remain disallowed.

> ## Actor reminders and jobs fail to register when their name or actor ID contains characters such as `|` or `@`
> ### Problem
> Registering an actor reminder through the Scheduler service failed when the reminder name, or the actor ID it belongs to, contained certain characters such as the pipe `|` or at sign `@`.
> The same characters are accepted when invoking actors and when saving actor state, so an actor that worked everywhere else could not have a reminder created for it.
> The error returned in this case was also misleading:
> a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
> It claimed only lowercase names were allowed even though uppercase names are in fact accepted, and it did not describe which characters were actually rejected.
> ### Impact
> You were affected if you used Scheduler-backed actor reminders (the default since 1.15) and your reminder names, actor IDs, or scheduled job names contained characters outside the strict DNS-1123 set, for example `|`, `@`, or uppercase letters.
> ### Root Cause
> The Scheduler composes each reminder or job into a single name of the form `actorreminder||<namespace>||<type>||<id>||<name>` (or `app||<namespace>||<appID>||<name>` for jobs), using `||` as an internal delimiter.
> Each `||`-delimited segment was then validated against Kubernetes' DNS-1123 subdomain rules, which only permit lowercase alphanumeric characters, `-`, and `.`.
> This was far stricter than the character set Dapr already accepts at its API edge, producing the inconsistency between actor invocation and reminder registration.
> Because the validator lowercased each segment before checking it, uppercase names passed in practice while the surfaced error still referred to lowercase-only RFC 1123 subdomains.
> ### Solution
> The Scheduler now validates names using the same policy Dapr applies at its API edge, so anything accepted for actor invocation can also be used for a reminder or job.
> Reminder names, job names, and actor identifiers may now contain any character except `/`, `\`, `#`, `?`, control characters (including the NUL byte), and the exact path sequences `.` and `..`.
> Uppercase letters and characters such as `|` and `@` are allowed, and `||` continues to be accepted within actor IDs and names.
> - [Actor reminders and jobs fail to register when their name or actor ID contains characters such as `|` or `@`](#actor-reminders-and-jobs-fail-to-register-when-their-name-or-actor-id-contains-characters-such-as--or-)

## Other changes (2)

- Scheduler validation errors identify disallowed characters
- Scheduler validation errors now identify disallowed characters

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
