Support emails bouncing
Hey there, I'm on a Pro plan and having an issue. I sent an email to [email protected] yesterday. Today I got an error email from gmail:
The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720 [railwayapp.com 52.71.57.184: timed out] [railwayapp.com 54.209.32.212: timed out]
I tried from a different email address today, same issue.
I can't even send a message from https://railway.app/account?p=support because it looks like it doesn't properly populate my Project/Environment/etc options.
I know it's the holidays/weekend so obviously I wasn't expecting an instant response, but having no way of reaching support is a little scary 😂
Fix bounced or rejected emails - Gmail Help
For a number of reasons, recipients’ email servers can reject emails that you send. Gmail returns a message reflecting the response provided by the recipient’s server. Below, find common error messag
22 Replies
Project ID:
N/AN/A
Thread has been flagged to Railway team by @Brody.
but in the mean time, is this something the community can help with?
Thanks! I think I'm beyond community help here, seems like a bug with a cron task not triggering.
railway cron? not triggering at all, or triggering at the wrong times?
Not triggering at all (although the task works fine if I trigger it manually from the dashboard)
I can create an identical task in another project and it triggers just fine.
the dashboard even correctly indicates when it should run next, just never does
can you provide the project id?
f2dc3dd8-652d-44c2-857c-818878b88702okay please wait for a reply from the team here
@Cooper - you probably want to see this as well
Uhh. @Ray since oncall
Interesting. I was able to send just fine
If this is an ongoing problem, it has certainly not slowed the rate of new tickets via email.
Oh found it!
You were emailing: [email protected]
Not [email protected]
Did you find the other email somewhere? We don't to my knowledge own the railwayapp.com domain.
Hi. Looks like we’re good re: the incorrect email?
(Thomas is on call btw.)
🤦 no idea how i even managed that
sorry y'all i will pester you with support emails shortly
What’s your cron value, wavparty?
(but i've tried all kinds of different frequencies)
Went PD let me know if that's not accurate
Solution
Could you try
0 * * * *?(yep it's accurate, was awaiting handover before taking over)
hey yeah, as @Ray called out here I was somehow using a 6 digit cron value which looks like it gets parsed one way on the frontend and a different way on the backend. glad i was able to continue the theme in this thread of me doing everything in an inexplicably weird wrong way. 😆
thanks for the help everyone, happy new year
I'd just like to point out that you did absolutely nothing wrong with the cron, if the backend thought the cron was invalid than so should the frontend.
PRO-1644 - Cron schedules are not rejecting invalid cron syntaxes
0 0 * * * * is invalid, but registers as a valid "every hour" schedule on the front-end. The backend also does not inform the user that it's invalid - this causes confusion as everything appears to be normal, but the cron does not actually run.Status
Triage
Product