Errors showing up when run locally but not when deployed to gcp

[hplotly]

I have a dash app which displays error messages locally, but not in cloud run. Has anyone troubleshooted something similar?

I want the error messages to display (for example, when a user inputs incorrect data types). The problem is that they cannot see those errors in the cloud run app, so they don’t know that the models have stopped running.

[hplotly]

This is the kind of error I am talking about…Can see it when run locally but not when deployed to cloud run

[AnnMarieW]

Hi @hplotly and welcome to the Dash community

You might find this post helpful:

Error Handling for Callbacks and Layouts

Good day, All, I wanted to pass along something that I’ve learned recently. It is how we can utilize custom error handling of Dash callbacks and layouts once a server is deployed, and or you cant watch the console all the time. Also when running a flask server instead of running the app, even with debug=True, you lose the error messages. Anyways, to utilize this, we are going to add decorators to all the callbacks and layout functions. TLDR: import dash from dash._callback import GLOBAL_CAL…