Moe Shehab

@MoeNick @aminlatifi I don't see how this error is related to how things are hosted or how we check things in our pipelines. To me, this seems like an error...

@MoeNick @divine-comedian There is no enough context to what this issue is about or how it can be reproduced. Also we already have an auto-restart policy for our deployments when...

Yeah this can be closed now @jainkrati it has been resolved

Thanks @mohammadranjbarz I see it's hard-coded in the code of `bootstrap.ts`. Do you think we should give it the flexibility to be in `process.env` maybe that we can decide on...

So I think the only thing we should do to integrate this with the test step in the CI is this: ``` - name: Run tests run: npm run test...

Thanks @mohammadranjbarz I've added the above steps, it seems that when testing on real database data, the tests fail from the start. Please check this: https://github.com/Giveth/impact-graph/actions/runs/6145025837/job/16671618590

This issue seems to be very general. But from what I understood, we need a way to improve alerting on the logs based on the URGENCY or IMPORTANCE or CRITICALITY...

> @mohammadranjbarz For fatal errors I suggest using Ortto API and its dashboard that we already have. so it's like the logger system will log and Ortto will send emails...