@atripp The links are very helpful... BM always showing the time in UTC...though I updated the server time to be localtimezone. So, the scheduling automatically changes the next run to be in the UTC format... once this is understood, I see that the cron based scheduling is working as expected... Thanks for your help.

Okay, that isn't a good end-user experience. I switched to IIS hosted site and don't see this happening anymore now. Thanks for quick response. -Sri

@atripp this is great. Thanks. -Sri

Hi @sbolisetty_3792, What version of BuildMaster are you running? It looks like the third-party Slack extension was built using the legacy SDK and extension model, which will not work in BuildMaster 6.2. We recently added documentation on how to POST to Micorosft Team's Webhook connectors. You could very easily adapt this to Slack by creating a new WebHook in Slack and posting to the Slack WebHook URL instead of the Teams Web Hook URL and tweaking the message text you are POSTing. Here would be an example Slack JSON to POST: {"text": "**BuildMaster - New Build** $ApplicationName $ReleaseNumber.$BuildNumber has completed. View it at [Build $BuildNumber]($BuildMasterUrl(release))."} Note: $BuildMasterUrl() is only available in 6.2.21+ Hope this helps! Thanks, Rich

Hi @sbolisetty_3792 , just to let you know, this will be fixed in the next maintence release of BuildMaster (BM-3654). Basically, if a Server has a Single environment, then that environment will be used for credential resolution. HOWEVER, note that this won't work for your dev-cap server because it's in two environments. So in that case, you couldn't use an environment-specific credential.