Say I have a callback with multiple inputs, and one of the inputs is a button that hasn’t been created yet (gets created by another callback). And I have suppress_callback_exceptions = True. If I try to trigger this first callback from another one of the inputs that has been created, does Dash still prevent the callback from firing? Asking because this appears to be the behavior happening in my script, and I can’t think of any other reason for my callback not firing. If this is the case, is there a way around this while still leaving suppress_callback_exceptions True, like providing some placeholder value for the button input that hasn’t been created?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| 'suppress_callback_exceptions' not working | 1 | 408 | January 10, 2023 | |
| Suppress Callback Exceptions not working for States? | 1 | 1962 | July 2, 2020 | |
| Can I have a `clientside_callback` depend on an input that "maybe" not exist on the page yet? | 5 | 288 | December 4, 2023 | |
| Help: Just Creating a Button in code calls its callback, even when it's not clicked | 5 | 665 | February 27, 2019 | |
| Callbacks fired even if components not on page (dynamic layout), possible bug? | 0 | 332 | July 23, 2019 |