We are looking into an issue with time cards not processing correctly over night. Our team is working quickly to find and solve the issue.
On our main server last night we had an issue with the time server. You may notice some early morning time cards off we are investigating the cause. You may need to manually fix some of those time cards. Sorry for the inconvenience.
Issue has been resolved
Our CA data center is having an issue and our team is investigating.
Ce soir, nous ferons l'objet d'une mise à jour de la base de données à 00h30 HNE. Pendant cette période, le site sera indisponible. Nous nous attendons à ce que cela prenne jusqu'à 3,5 heures. Désolé pour le dérangement.
Saturday, April 22 we will be updating our servers to increase speed and performance. We expect this to take 2hrs. We will start this at 12:30a EDT.
Tonight we will be updating our servers to increase speed and performance. We expect this to take 2hrs. We will start this at 12:30p EDT.
Last night 5p est we had a short interruption to our Canadian servers. Our team found the issue and fixed it. Sorry for any inconvenience.
From 5:30a-6:30a EST we had an issue with our Canadian data center. Punches may have not been captured during this time. We are reviewing what happened and will put processes in place to reduce the likelihood of happening. We do apologize for the inconvenience.
Last week one of of servers had an issue with automated tasks. We resolved the issue last week however discovered today the weekly schedule reminder emails did not go out as expected. This has been fixed. Sorry for the inconvenience.
The issues with automated tasks have been resolved. We apologize for any inconvenience
We are currently investigating an issue affecting automated tasks on TimeWellScehduled. Affected areas include slower timecard processing and missed important date reminders. We apologise for any inconvenience.
We will be doing maintenance on the database servers tonight. This will start around 12:30a Nov 12 and last a couple of hours. We do not expect extended downtimes, just a quick reboot. During the maintenance window, the servers will respond slower than normal.
Over the last 2 days, push notifications and email alerts may have been slow to come or missed due to the previous server issues. Everything is running normally now. Sorry for the inconvenience.
Our team worked through the night and resolved the issues with our services. The fixes now show faster than before page load times. We do apologize for the last 2 days issues.
We are still experiencing issues with our database server at times. You may notice slowness. Our team is working to fix this ASAP and do apologize. All hands are on deck. Nous rencontrons encore parfois des problèmes avec notre serveur de base de données. Vous...
We have reviewed the issue and restarted all services. Speed issues are resolved. If you have any more issues please reach out to support. We apologize for the inconvenience.
We have reports of slowness and our team is investigating. Update to come.
On June 12 2am EDT we will be updating our database server. We expect to be down for 20 to 30min. Access to the site will not be available to those clients on our USA server.
Our database server is acting up and slower than normal. Our team is working on it.
Tonight we will be running some database updates starting at 11pm EDT. Services will still be available, but might take a little longer to respond. Sorry for any inconvenience.
Tonight we will be undergoing a database update at 1am EST. During the time the site will be unavailable. We expect this to take up to 3hrs. Sorry for the inconvenience
All email issues have been fixed and messages are flowing.
Our mail server appears to be down. Messages are being queued. We are working on it with our data center team.
We are experiencing issues across all systems, we believe our cloud provider might be down. We are working on resolving right away.
We will be updating our database tonight. We expect a short down time as make this update. Unfortunately this may require the entire system to be down while we do this.
We are experiencing issues with the TimeWellScheduled employee app. Our team is working on resolving the issue. You may not be able to connect at this time.
Tonight we are running a few database updates to enhance performance. This may cause service interruptions and apologize for the inconvenience.please back date it to 10pm nerdtime
Google has fixed the issue, details are here – https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh
Load Balancer Issues – Google is having an outage which has brought down TimeWellScheduled.
We are waiting for Google to address – https://status.cloud.google.com/
We are experiencing intermittent server issues. We are Currently investigating the issue with the Team and hoping to has a resolution soon.
Our apologies to our CA datacenter clients, our SSL certificate has an issue this morning.
It has since been resolved.
Sorry for any inconvenience.
We've noticed slowness on our servers. Our team is working on it and cycled the servers. We apologize for any inconveniences.
This weekend we will be doing some routine maintanence. On Sunday March 28 9pm-11pm EDT. The servers will be slower to respond to requests. Sorry for any inconvenience this may c
We've made some server changes to increase performance and will be adding move systems to help support the new employee app.
We have found one cause of the server issues this weekend. It seems the employee app jumped in download/usage by over 100% in a 24hr period causing an unexpected load on our servers. We are working to make an update to manage the loads better. Apologize for the...
There was a delay in emails leaving the site - unrelated to the server slowness. We have found the issue and resolved, emails are flowing again.
We are still working on the server issues - it seems the servers are running much harder than normal. We are still working with our entire team to find a fix
Small hiccup on one of the servers. All fixed now.
One of our servers is experiencing an issue and causing some clients to be unable to access. We are aware and working on it with our data center team.
For the last 20hrs we've had issues with the mail server that may have delayed or even prevented messages from going out. The issue has been fixed. Sorry for the inconvenience.
We completed all server and infrastructure fixes as of 5pm yesterday. In the end we brought another server online to address the load. We are very sorry for the inconvenience this caused and will be watching the entire system closely the next few days.
Just a quick update, it looks like we had some sort of denial of service hit on our hosting environment. We are taking measures to fix this ASAP.
We've noticed one of our servers responding shortly. Hosting is looking into this and addressing the issue. We expect to be down for a short moment. Update 11:30am - It looks like we are being hit with an overload of requests. We are not sure why, we are working on...
Sorry we had a replication issue on one of the servers that was fixed 10min ago. It only impacted 1 of the servers. Sorry for the inconvenience.
We do apologize for the past few weeks and slowdowns you experienced. We have made several code and server updates to address these issues. As well, we have found specific conditions that caused our servers to be queried more than they needed too. We will keep...
We have noted some slowness and rebooted all systems.
Starting at 12am EDT today, Mar 22 we will be doing a database upgrade to the server. This *may* cause slowness from the system as we make this change. All changes should take less than 2 hours.
Earlier this morning our systems came back online, back to our original setup. Google is still investigating and will keep us posted. Performance should no longer be slower than normal. Thank you for your patience as we worked through this.
Our team is still working with Google to solve the server issues from last night and today. Just wanted to share that the issue was not directly at our level, but google's cloud services (you can see here https://status.cloud.google.com). Here is a snippet from their...
We may have temporary outages through the day as Google works to restore out primary servers. The downtime should be minimal when it happens. We are also running on a single server (vs our normal 2) so if the site seems a little slower than normal, that is why.
Out SSL server that was down is now back up. Sorry for any inconvenience, we are working with Google to pinpoint what happened and put steps in place with them to avoid it in the future.
We have another service issue, google's servers are down with our SSL server (this is the service that provides the secure connection). We already have a ticket in with google and working with them to resolve. Will keep this updated.
Google is still investigating what happened - they are unsure. It looks to be a physical server issue. On our side, we've launched a new instance and we are up and running. If you notice a speed issue, we apologize and this will be fixed once Google has solved the...
We've discovered the issue is with google maintenenace migration. We're working with our google support to fix the issue.
There appears to be an issue with our Google Cloud server - we are looking at a restart to fix the issues. Should only be down for a few minutes.
We’ve discovered an issue with our certificate and as such, the app may stop working. We are working with Apple to get this sorted out ASAP. In the mean time, if the app stops working for you, please use the web browser on the device and set the URL to your company...
Over the last 2 days we have experienced some database server issues which have resulted in slow speeds. We believe they were all addressed last night with a few updates and everything will run normal on the go forward. Very sorry for any inconvenience this has...
Our main server will go offline Sunday June 10 11:59PM EDT for 2-3 hours. We will be upgrading our servers at that time.
Our main server will go offline from May 6 11pm to May 7 3am EDT. We will be upgrading our servers at that time.
We have resolved the minor Timecard issue. Everything is now back to normal.
We have reports from a few users that the timecard page is intermittently working. Our team is looking into this.
Our apologies for a brief downtime this morning, the SSL certificate on one of the servers wasn't working. It has since been resolved and workin
Currently, we are receiving reports from some clients that they are unable to connect. We are working on the issue and will have it resolved ASAP
We discovered earlier today that TimeWellScheduled was inaccessible for Bell clients due to a service issue with Bell internet. TimeWellScheduled servers are monitored by a third party. Our server status can be viewed in real time here:...
Weekly schedule reminder email issue Some employees may have received their weekly scheduled with incorrect information. The department they were scheduled in may have not been the correct department. We do apologize for any inconvenience this has cause
Over this weekend, we will be making upgrades to our servers. These changes will speed up access to the site and decrease load times. These upgrades will happen after hours, starting at midnight EST for a couple of hours.
Our unscheduled maintenance has completed. Service are now be back to normal. Very sorry for any inconvenience.
TimeWellscheduled may be slower than usual this morning (July 25, 2017) due to unscheduled maintenance to our server. The development team is working hard to speed things up. Service will continue as normal, just be aware of slower response times.
Our team has been working hard over the last week making small but necessary changes to the system. With this, comes faster load times and quicker reports. We do apologize for any inconvenience and appreciate your patience.
We have found an issue that causes the site to take a long time to load when using the biometric device AND not punching the correct action. If the employee is punching the correct action, meaning they are pressing ENTRY at the start of the shift, NO ISSUE. Only if...
A few companies may have had issues with their Easypay export, specifically stating there was errors with the department code. Last week we made an update to the export for those stores that export based on department worked (not the employees primary department) ,...
We've found a simple work around to continue using Firefox with the Biometric Scanner. Deactivate Auto update in Firefox Download firefox 51.00 - Link to firefox 51: https://ftp.mozilla.org/pub/firefox/releases/51.0/win32/en-US/Firefox Setup 51.0.exe Close Firefox...
Today we found out that Firefox has discontinued support for Java in the latest version (V52) release. Java is a critical component for biometric operations. If your store is using a biometric finger scanner please update your browser to Internet Explorer...
As part of our process to improve our systems, we need to upgrade our database servers. From 1AM to 4AM (EST) on Nov 13 we will have a service interruption that will make the service unavailable. If you have staff who need to punch in, please look at using our offline...
As a result of the service interruption over the weekend we've updated the TmeWellScheduled app. As well, processes have been put in place to avoid this same failure in the future.
We've released a new Version of the TimeWellScheduled iPad app to resolve the earlier service interruption.
We are experiencing a brief interruption of service to the TimeWellScheduled iPad app. We expect to have the issue resolved shortly.
We're back up and you can read about the google outage here: /timewellscheduled-may-be-unresponsive-august-22-2016/
We just got word that google’s servers (where we host TimeWellScheduled) are down so response times may be delayed. If you haven't already , you can turn on TimeWellScheduled's "Offline mode" to help things run smoother. Make sure you are using the latest Firefox...
(April 17, 6:34PM) Today we experienced an unexpected outage on TimeWellScheduled service from 12:30pm to approximately 3:30pm. Clients that were using TimeWellScheduled in Offline Mode continued to be able to punch in and out without any difficulties. To enable it...