# Is suppress\_callback\_exceptions no longer supported in Dash v1.11.0 **URL:** \ **Category:** Dash Python\ **Created:** [April 18, 2020, 5:43pm UTC](https://community.plotly.com/t/is-suppress-callback-exceptions-no-longer-supported-in-dash-v1-11-0/38005 "2020-04-18T17:43:09Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![flyingcujo](https://avatars.discourse-cdn.com/v4/letter/f/e480ec/32.png) [@flyingcujo](https://community.plotly.com/u/flyingcujo)\ **Post date:** [April 18, 2020, 5:43pm UTC](https://community.plotly.com/t/is-suppress-callback-exceptions-no-longer-supported-in-dash-v1-11-0/38005/1 "2020-04-18T17:43:09Z")
I upgraded my multi-page app from v1.10 to v1.11 and is appears that the `suppress_callback_exceptions=True` setting no longer works. Has this been depreciated and we now need to rewrite our callbacks in the pattern-matching format? ---
**Author:** ![flyingcujo](https://avatars.discourse-cdn.com/v4/letter/f/e480ec/32.png) [@flyingcujo](https://community.plotly.com/u/flyingcujo)\ **Post date:** [April 18, 2020, 6:52pm UTC](https://community.plotly.com/t/is-suppress-callback-exceptions-no-longer-supported-in-dash-v1-11-0/38005/2 "2020-04-18T18:52:00Z")
`A nonexistent object was used in an `Output` of a Dash callback. The id of this object is `delete-bulk` and the property is `style`. The string ids in the current layout are: [chart-options-store, TimeZonePicker, DatumPicker, hilo-data-store, station-gps-store, session-data-store, highlight-store, url-sources-store, auth-user, reset-layout, slider-marks, aws-data, yearly-aws-data, user-data, delete-status, email-list, data-conditional, url, page-content]` ````auto (This error originated from the built-in JavaScript code that runs Dash apps. Click to see the full stack trace or open your browser's console.) ReferenceError: A nonexistent object was used in an `Output` of a Dash callback. The id of this object is `delete-bulk` and the property is `style`. The string ids in the current layout are: [chart-options-store, TimeZonePicker, DatumPicker, hilo-data-store, station-gps-store, session-data-store, highlight-store, url-sources-store, auth-user, reset-layout, slider-marks, aws-data, yearly-aws-data, user-data, delete-status, email-list, data-conditional, url, page-content]``` at unwrapIfNotMulti (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34632:15) at http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34750:26 at Array.map () at http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34749:42 at Array.map () at _callee3$ (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34735:40) at tryCatch (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/polyfill@7.v1_3_0m1586525360.8.7.min.js:1:93205) at Generator.invoke [as _invoke] (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/polyfill@7.v1_3_0m1586525360.8.7.min.js:1:92979) at Generator.t. [as next] (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/polyfill@7.v1_3_0m1586525360.8.7.min.js:1:93737) at asyncGeneratorStep (http://127.0.0.1:8050/_dash-component-suites/dash_renderer/dash_renderer.v1_3_0m1586525370.dev.js:34512:103) ```` ---
**Author:** ![Emil](https://sea2.discourse-cdn.com/flex024/user_avatar/community.plotly.com/emil/32/31734_2.png) [@Emil](https://community.plotly.com/u/Emil)\ **Post date:** [April 18, 2020, 7:23pm UTC](https://community.plotly.com/t/is-suppress-callback-exceptions-no-longer-supported-in-dash-v1-11-0/38005/3 "2020-04-18T19:23:42Z")
What you are experiencing is known behavior. There are ongoing discussions on how to handle the issue, > [@mega Dash v1.11.0 Release - Introducing Pattern-Matching Callbacks](https://community.plotly.com/t/dash-v1-11-0-release-introducing-pattern-matching-callbacks/37592): > > Update: [version 1.16 has been released](https://community.plotly.com/t/dash-1-16-0-brand-new-debugging-performance-tools-improved-callback-graph-date-axis-timeline-improvements-faster-images-content-security-policy-and-community-contributions/44776) since this was posted. Dash v1.11.0 is a minor release introducing the new Pattern-Matching Callbacks feature and providing multiple bug fixes improving the performance, robustness and behavior of Dash callbacks. Official Changelog [Dash v1.11.0](https://github.com/plotly/dash/releases/tag/v1.11.0) Highlights New [Pattern-Matching Callbacks](https://dash.plotly.com/pattern-matching-callbacks) feature that allows you to write callbacks that respond to or update an arbitrary or dynamic number of components ([PR #1103](https://github.com/plotly/dash/pull/1103)) Multiple bug fixes for callbacks, includi… For now, a possible solution/workaround is, > [@ReferenceError in multipage application](https://community.plotly.com/t/referenceerror-in-multipage-application/14497/8): > > While not a real solution to the problem (which i have not yet understood fully; it seems to happen only in some cases), i have come up with a workaround using the new Dash pattern matching callbacks in [megaphone Dash v1.11.0 Release - Introducing Pattern-Matching Callbacks](https://community.plotly.com/t/dash-v1-11-0-release-introducing-pattern-matching-callbacks/37592/7). Let’s say that the problematic callback looks like this, @app.callback(Output(SITE\_HEIGHT\_CACHE, 'data'), [Input(SITE\_HEIGHT\_SLIDER, 'value')]) def update\_site\_height(value): return value with th… ---
**Author:** ![flyingcujo](https://avatars.discourse-cdn.com/v4/letter/f/e480ec/32.png) [@flyingcujo](https://community.plotly.com/u/flyingcujo)\ **Post date:** [April 18, 2020, 11:34pm UTC](https://community.plotly.com/t/is-suppress-callback-exceptions-no-longer-supported-in-dash-v1-11-0/38005/4 "2020-04-18T23:34:28Z")
Thanks @Emil! I’ll wait for the next version before upgrading.