smapOne had 19 outages in the last 2 years totaling 251h 20m of downtime — averaging 0.8 incidents per month.
There were 19 smapOne outages since July 3, 2024 totaling 251h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
The smapOne platform has a partial outage. We are working on the solution and we will inform you here as soon as the platform is fully available again.
The smapOne platform is available again.
Yesterday evening, our platform experienced an outage that resulted in a service disruption of approximately 60 minutes. During this time, the platform was not accessible. In addition, email notifications and webhooks were partially impacted and operated with limitations until approximately 09:00 this morning. The issue has now been fully resolved, and all systems are operating normally again. The root cause was identified as an error in the network configuration of a central system component. Our team has corrected the configuration and taken steps to prevent similar issues in the future. We sincerely apologize for the inconvenience this incident may have caused and appreciate your patience while we worked to restore full service.
The smapOne webapp has an outage. We are working on the solution and we will inform you here as soon as it is fully available again.
The smapOne WebApp is available again.
We are currently experiencing an issue opening drafts and tasks from some smaps in the smapOne app. We are currently investigating the problem and looking for a solution.
The problem has been identified and a bug fix is being developed. A new version of smapOne will be uploaded to the stores later today.
The bug fix has been created and the new version has been uploaded to the respective stores. As soon as the version has been successfully checked by the stores, the new versions will be available for download.
Bugfix is now on all platforms ready for download.
Derzeit untersuchen wir Meldungen, dass die smapOne Plattform nicht mehr zu erreichen ist. Erste Ergebnisse liefern ebenfalls Informationen, dass Microsoft Azure auch Störungen meldet. Wir untersuchen die Zusammenhänge und halten Sie auf dem Laufenden.
Die Ursache ist ein Fehler in den Microsoft-Systemen. Microsoft ist an einer Lösung dran. Weitere Infos gibt es unter https://azure.status.microsoft/de-de/status
Microsoft ist dabei die Änderungen an ihrer Infrastruktur zurückzurollen und erwartet, dass die Systeme innerhalb der nächsten 3,5 Stunden wieder lauffähig sind. Uns erreichen inzwischen Berichte, dass smapOne von manchen Nutzern wieder erreicht werden kann. Wir informieren, sobald wir mehr wissen oder wieder normal verfügbar sind.
Unsere Monitorigdaten deuten darauf hin, dass die smapOne-Umgebung wieder weitestgehend normal erreichbar ist. Die Menge an Anfrage ist wieder in gewohnten Bereich. Selten schlagen noch Anfragen fehl, diese sollten aber bei einem erneuten Versuch funktionieren. Da Microsoft laut ihrer Statuspage den Fehler noch nicht vollständig behoben hat, beobachten wir weiterhin die Situation.
Der Fehler wurde behoben. Die smapOne steht wieder normal zur Verfügung.
Following a major update to our Code Scanner software, some barcodes are no longer being read correctly. In addition, a few devices are crashing. We are currently working on identifying and fixing the problem.
Fix for code scanner brick is live in iOS and Android with AppVersion 25.9.22
We've detected issues in sending data and forwarding tasks. We're currently investigating and will solve the issues as soon as possible.
We've found the issue and will solve it in the next appr. 10 minutes.
We've found the issue and will solve it in the next appr. 10 minutes.
This incident has been resolved.
We are experiencing a peak load that is making our systems slow. We are currently looking for the source and working on a solution.
We have found the source that has slowed down our systems. We were able to stabilize the platform. We are continuing to monitor the behavior and the stability.
This incident has been resolved.
We are currently investigate the problems.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We experienced a problem with emails and webhooks triggered from Data records: These notifications were not sent. What Happened? Our last release caused errors concerning tasks that are done in the background. What Have We Done? We rolled back to the version before and requeued all pending emails and webhooks. It will take a while to process all of them. We will inform you, when all are processed. What Should You Do? Please be patient. We will process all outstanding notifications. Contact: You can reach us anytime in the community or contact our support directly via email at [email protected]. We are here to assist you! Thank you once again for your understanding and patience.
All pending emails and webhooks have been processed. If you experience further issues please contact our support at [email protected]
Who is affected? Everyone who uses external data access links to download of multiple pdf reports for a smap version. Workaround: The Creator of the smap can still download all reports. With the external data access link, each pdf can still be downloaded individually via the detailpage of a data record. We are in the process of solving it as quickly as possible
This incident has been resolved.
There are currently various malfunctions such as unreachable pages. We are looking for the cause and are trying to find a quick solution.
The system has been stable for several hours. The case is closed. We have been following the reports over the last few hours. We suspect external reasons for the few cases of malfunction in the morning.
Who is affected? Automations that are downloading pdf reports for single data records via preview routes (like /Backend/preview/Smaps/[smapid]/Versions/[version]/Records/[recordid].Pdf) since 20.1.25 from 9:32 am Error behavior: Due to an internal change pdf is not recognized as a valid data record export format. Workaround: use /Backend/intern/Smaps/[smapid]/Versions/[version]/Data/[recordid].Pdf instead We are in the process of solving it as quickly as possible
We are continuing to work on a fix for this issue.
The issue has now been fixed, and the preview routes are functioning as expected.
The smapOne Community Forum has an outage. We are working on the solution and we will inform you here as soon as it is fully available again.
This incident has been resolved.
Who is affected? Automations that download reports (pdfs, Word) and were executed in the period from 12:00 -15:20, and where the file name for the reports was taken from the header data of the smapOne platform. Error behavior: Due to a change in the format in which the header data is transferred, the reports may have been saved with the wrong file name. Details: The format of the header was changed from “Content-Disposition”: “inline; filename=>” to “Content-Disposition”: “attachment; filename=>”. The change has been reverted and all downloads work as usual again.
We detected a problem with our background worker for data records at 12:45 p.m.. Therefore, emails for data records won't be triggered as well as webhooks belonging to the respective automations. The problem seems to be live since 10:45 a.m. and is relevant for every data record. The issue will be fixed in 10 minutes. Emails which have queued for the time since the issue will be triggered manually from our side. We will keep you in the loop.
The issue has been fixed. Every new data record will be sent as usual or with a short delay due to the amount of waiting emails. The emails from the time of the incident have been triggered again and will now be sent by our system. This may take up to two hours until every email has been sent and web hooks react accordingly.
The incident had been resolved. All emails from the start of the incident now have been sent. All webhooks will have been triggered as expected. All newly created data records work as usual again.
We’ve detected an issue for users who registered themselves during the past 23 hours via 3rd party login, meaning using Microsoft login with Entra ID. These users are not able to login currently via Microsoft. All other users registered by 23.10.2024, 11 a.m. and earlier are not affected by this incident. We’re currently working on a fix and are kindly asking for a short amount of patience. We’ll keep you updated.
The issue has been resolved. Everyone can log in again.
Currently there are some problems by microsoft. Influence on our platform is not foreseeable. For more updates look at https://azure.status.microsoft/status
We are monitoring the situation.
All problems are solved.