You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Using pattern matching ALL for running argument fails when the list is empty #3297
When using pattern matching for the running argument (ex: running=[(Output({'type': 'loading', 'id': ALL}, 'display'), 'show', 'hide')]), if there are no components on the page dash throws the error: state.paths.objs[idKey] is undefined
Describe your context
Please provide us your environment, so we can easily reproduce the issue.
replace the result of pip list | grep dash below
dash 3.0.4
Describe the bug
When using pattern matching for the running argument (ex: running=[(Output({'type': 'loading', 'id': ALL}, 'display'), 'show', 'hide')]), if there are no components on the page dash throws the error: state.paths.objs[idKey] is undefined
Expected behavior
No error, no side updates (since there are no components)
Thanks for the report, I was playing around for the first time with pattern-matching callbacks in a running argument and didn't know where this cryptic error from dash clientside was coming from 😅.
Activity
fgoudreault commentedon Jul 31, 2025
Thanks for the report, I was playing around for the first time with pattern-matching callbacks in a
runningargument and didn't know where this cryptic error from dash clientside was coming from 😅.