徽章下载及时出道.
- investigating
我们的一些管理员目前遇到一个问题,在点击下载徽章的链接时,下载出错.
- identified
这一问题已经确定,一个解决办法正在实施之中.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
60 Clever incidents · 2024年9月 — official updates, affected components, duration and resolution details.
我们的一些管理员目前遇到一个问题,在点击下载徽章的链接时,下载出错.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
Clever is in the process of updating our website. You may notice some minor changes or possible errors on our home page during this update, but it will not impact our customers' ability to login or use our products.
Our website update is still in progress.
This incident is resolved. We have completed the update to our main website.
5:08至5:59 pm PST之间,一些用户可能无法登录到"聪明门户"或"推出"应用软件. 服务恢复了,我们正在监测它。 如有其他问题,请联系支援小组. Clever.com.
自动翻译自官方事件更新。
今天7:12至8:53 AM PT, 一个名为“1应用程序等待您”的任务被错误地显示给在窗口期间登入智能仪表板的区管理员。 这项任务参考了另一个地区待处理的申请邀请,只针对该地区。 它已经被移除了。 任务只链接到您的应用程序页面; 因此没有共享、 更改或访问数据, 不需要行动 。 如果它还在出现,请刷新仪表板,你应该看到它改正。 我们为混乱而道歉.
自动翻译自官方事件更新。
聪明人知道一个服务中断 影响销售部队, 我们依赖第三方平台 部分支持案件管理。 因此,您可能会遇到延迟支持案件更新,电子邮件通知与案件绑定,或者在通过受影响的渠道提交新的支持请求时,反应时间会更慢. 这个问题起源于销售力量,不在我们的基础设施之外。 我们的小组正在积极监测局势,一旦Salesforce解决了干扰问题,将恢复正常的支助工作流程。 核心智能服务(同步,上市,登录)不受此事件影响. 我们会在这里发布更新 随着我们学到更多。 谢谢你的耐心.
Salesforce在其状况网页https://status.salesforce.com/上公布,他们已经查明并正在努力解决这一问题。 我们没有时间框架来估计 什么时候能解决聪明人的问题 但我们在监视他们的状况 我们会在这里发布更新 随着我们学到更多。 谢谢你的耐心.
销售部队为早先的服务中断安装了固定装置。 以前受到影响的所有渠道现在都正常运行,支助案件处理、通知和反应时间已恢复到预期水平。 我们将继续监控 销售力量推出更多更新 防止再次发生 如果有任何变化,将再次发布。 谢谢你在这起事件中的耐心.
销售部队已经解决了这一事件。 以前受到影响的所有渠道现在都正常运行,支助案件处理、通知和反应时间已恢复到预期水平.
自动翻译自官方事件更新。
聪明人目前正在调查一个问题,即连接的应用网页上的同步时间在仪表板上显示不准确. 一旦我们得到更多信息,我们将提供最新情况.
这一问题已经确定,一个解决办法正在实施之中.
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们意识到目前影响一些API同步的问题,并正在积极调查我们的结局。 我们将尽快发布更多信息。 我们对此可能造成的任何不便表示歉意.
Aeries API syncs that were previously showing a sync error are now syncing to Clever. We will continue to monitor the situation. If you have questions, please submit a ticket to Clever's Support Team at support.clever.com Thank you
Aeries API syncs that were previously showing a sync error are now syncing to Clever. This issue has now been resolved and we appreciate your patience.
自动翻译自官方事件更新。
We’re aware of an issue currently affecting some Aeries API syncs and are actively investigating on our end. We will post more information as soon as possible. We apologize for any inconvenience this may be causing.
The sync issue with some Aeries API syncs has been resolved. We thank you for your patience.
We have identified an issue that is preventing some students from being able to access their Teacher Pages on the Clever Portal. Students and teachers are still able to access applications from their district Portal pages. We’re investigating the issue and will provide status updates.
This incident has been resolved.
We have identified an error causing Canvas IDP logins to fail. We are working on a resolution and will provide an update at that time. We apologize for any inconvenience this may be causing.
This incident has been resolved.
We have identified an error causing Canvas IDP logins to fail (Invalid or Unknown Client Error). We are working on a resolution and will provide an update at that time. We apologize for any inconvenience this may be causing.
This incident has been resolved.
We have identified an error causing custom login instructions and hints to disappear from the Clever login page. We are working on a resolution and will provide an update once these labels are restored. Action Required: If your users see a generic "Account" login page instead of your typical provider (Google, Microsoft Entra, AD, etc.), please update the SAML Authentication setting in your dashboard to identify your provider. For further assistance, please contact support.clever.com.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users may have experienced login issues to the Clever Portal today, April 15th, around 1:40pm ET/ 10:40am PT. This issue was resolved and everything is back to normal. If you see any additional issues, please contact Clever Support through our Help Center: support.clever.com.
Clever is currently experiencing intermittent login failures with an unknown cause. Our Engineering team is currently investigating the issue and we will update this page as soon as possible. We apologize for any inconvenience this may be causing.
The intermittent login failures have stopped and our team is still investigating the root cause of the issue. If you are still experiencing login issues, please contact our support team at support.clever.com. Thank you!
The incident regarding intermittent login failures has been resolved. -Thank you
There is a sync issue for some districts on the Skyward Selenium sync that is preventing syncs from being completed. At this time we are investigating the issue and will provide regular status updates. We apologize for the inconvenience this may cause.
Our Engineering team was able to identify and resolve the issue regarding Skyward Selenium syncs failing for some districts. Those impacted districts should see those previously failed syncs run. For any further questions regarding your impacted sync, please contact our Support Team at support.clever.com Thank you and we apologize again for any inconvenience this may have caused.
Clever is currently investigating an issue where clever.com/login is inaccessible. As soon as we have more information, we will provide an update.
Amazon AWS, a service that works with Clever, is experiencing a issue that is preventing users from being able to log in to Clever. We are monitoring the issue and will provide status updates as they become available.
Amazon AWS has resolved this issue, and everything is back to normal.
Clever is currently investigating an issue where the device camera is not opening when users are attempting to log in to Clever with a Badge on Windows devices. As soon as we have more information, we will provide an update.
This issue has been resolved. Users should now be able to use Badges to log in on Windows devices. For all other concerns, please reach out to our support team at support.clever.com
Some users on the new Clever iOS app are experiencing issues. For districts experiencing an issue where users had to enter their district information and login again after returning directly to the Clever app from a resource, this has been resolved as of 3:30pm PDT 1/15. If your district is still experiencing this, reach out to Clever Support at support.clever.com. For districts experiencing a login loop issue requiring users login multiple times, Clever has fixed the issue in the latest Clever iOS app, v6.0.8, and estimate it to be available as an update on Apple by early next week. When this update is available, you can follow these instructions to update the app: https://support.clever.com/s/articles/360024746971?language=en_US For all other issues, please contact Clever Support through our Help Center: support.clever.com.
Some users on the new Clever iOS app are experiencing issues. For districts experiencing an issue where users had to enter their district information and login again after returning directly to the Clever app from a resource, this has been resolved as of 3:30pm PDT 1/15. If your district is still experiencing this, reach out to Clever Support at support.clever.com. For districts experiencing a login loop issue requiring users login multiple times, Clever has fixed the issue in the latest Clever iOS app, v6.0.8, and this update is available to download in the Apple App Store. Districts can follow these instructions to update the app: https://support.clever.com/s/articles/360024746971?language=en_US For all other issues, please contact Clever Support through our Help Center: support.clever.com.
This incident has been resolved. For districts experiencing an issue where users had to enter their district information and login again after returning directly to the Clever app from a resource, this has been resolved as of 3:30pm PDT 1/15. If your district is still experiencing this, reach out to Clever Support at support.clever.com. For districts experiencing a login loop issue requiring users login multiple times, Clever has fixed the issue in the latest Clever iOS app, v6.0.8, and this update is available to download in the Apple App Store. Districts can follow these instructions to update the app: https://support.clever.com/s/articles/360024746971?language=en_US For all other issues, please contact Clever Support through our Help Center: support.clever.com.
Clever is seeing some SAML login failures and is investigating the root cause, including whether there is any relation to ADFS as the IdP and outdated certificates. Please contact support at support.clever.com if you are experiencing widespread login issues across your district so our Engineering team can investigate further. We will provide updates as our team continues to make progress on this issue.
Clever is continuing to see some districts with SAML SSO display login failures with "Login with ADFS". We are still investigating the root cause. Please contact support at support.clever.com if your district is configured to use ADFS with SAML logins and sees this error message, "No success code received from your SAML server", in your Access Logs. We will provide updates as our team continues to make progress on this issue.
This incident has been resolved. For troubleshooting expired SAML certificates at your district, please see our Help Center article: https://support.clever.com/hc/s/articles/000001736?language=en_US For any further issues, reach out to Clever Support at https://support.clever.com/
Clever is currently investigating an issue that is causing some districts to see an error message when users are trying to log into Clever. As soon as we have more information, we will update this status page. We apologize for the inconvenience. Thank you
Our Engineering Department has implemented a fix and it still closely monitoring the situation. For questions or concerns, please contact Clever Support at support.clever.com. Thank you,
The login issue for some districts has been resolved. We apologize for any inconvenience this may have caused.