[misc]: how do we make it clearer why callbacks might fail

[juliusmarminge]

I understand that this issue may be closed if it should be filed in another category

• I understand

My issue

it feels like >90% of issues we get is related to misconfigured middlewares / auth rules.

when you know where to look, it's very easy to identify this. e.g. latest issue report resolved in 3mins after given a reproduction:

but it's not always possible to provide access to the repo and when constructing a minimal repro you might omit your auth layer.

so... how can we surface a nice error message to make it trivial to debug this misconfiguration?

What we already have:

• status in dash have a tooltip with the callback response, this is currently not set for dev uploads though
• section in FAQ

What we will have

• audit logs with file target filters

These all requires context switching away from your editor though, so there's no obvious hint in the editor / terminal why it might've failed

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 10 days. It will be closed in 5 days if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 10 days. It will be closed in 5 days if no further activity occurs.