Hubert Deng

It should be safe to do, looks like we do that in prod. I'm going to put up a PR to add this option to the post process forwarders.

If the directory doesn't exist in the first place, we still want to throw the same error so behavior wise I think this should be fine

@dlouzan I've added this in https://github.com/getsentry/self-hosted/pull/3085. Closing this issue as this has been completed

What is the source of your lag for your self-hosted instance? You may need to fix that before proceeding

Going to close this due to https://github.com/getsentry/self-hosted/pull/3116

Thanks for the feedback. I am going to close this issue since it looks to be resolved.

Those errors should not be happening when you're trying to bring your docker containers up. It indicates to me that your docker containers have not been properly built before running...

Just to be sure, is your sentry.conf.py specifying PyMemcacheCache as the backend?

As @aldy505 has mentioned above, have you checked the Sendgrid configuration itself?

Is your self-hosted instance TLS/SSL encrypted? Running out of ideas here...