Hmm, it's not super clear what the issue might be. Have you tried redeploying (rather than restarting) the service? It's possible a fresh pull will be helpful. Thanks.

Hi,

I already tried to do this, I did a redeploy and I also restarted postgree and this intermittent log continues

I would recommend looking for answers and solutions from places like stack overflow as Postgres would not be something specific to the Railway platform.

Okay, I'll try, thanks

I did a little googling and found the workers are part of the timescale implementation, here are some potentially helpful resources:

• https://docs.timescale.com/api/latest/informational-views/job_errors/#error-retention-policy

• https://www.timescale.com/forum/t/failed-to-start-a-background-worker-error-timescaledb/56

• https://docs.timescale.com/self-hosted/latest/configuration/telemetry/

It's interesting that we haven't seen this before (or Brody can correct me on that), but we'd be keen to understand if it's something we could/should adjust in the image.

Hello, thank you for your explanations, they helped a lot, and now we can close this topic. Thanks

Closing the topic now. Thanks