Resolved -
Our team discovered a service disruption that impacted CSV data uploads via the Sense SFTP integration and related API processing on May 6, 2025, from 3:00am PST to 7:20am PST (or 10:00 UTC to 14:20 UTC).
During this time window, files uploaded via SFTP were not processed, and some data updates submitted through the Sense API may not have been successfully applied. Affected requests would have returned a 400 or 500 error. This has been caught by our team and corrected from persisting.
At this time, all services are now fully operational. A full post-mortem is underway to prevent recurrence and strengthen deployment and alerting practices.
If you uploaded files or pushed updates on May 6, 2025, between 3:00am PST to 7:20am PST, please reprocess or retry those updates.
If you need support with identifying failed updates or require assistance, please contact us at support@sensehq.com. We sincerely apologize for the inconvenience and appreciate your understanding and partnership.
May 6, 03:00 PDT
Resolved -
After monitoring, our team has confirmed that the fix put in place did resolve the issues we were seeing with Workflow events not processing intermittently. We will continue to monitor and ensure this does not recur in the future.
If you believe you are still experiencing issues, please reach out to our Support Team and submit a ticket here https://support.sensehq.co/hc/en-us/requests/new for us to investigate further.
May 2, 11:00 PDT
Monitoring -
Our team has identified the issue and has put in a fix to resolve these events from not sending out. We are showing stability across the platform once more, and will continue to monitor all Workflows to ensure we don't see this recur.
If you believe you are still experiencing issues, please reach out to our Support Team and submit a ticket here https://support.sensehq.co/hc/en-us/requests/new for us to investigate further.
May 2, 09:36 PDT
Investigating -
We have received reports of Workflow Events not sending out as expected for intermittent nodes. Our team is actively investigating this issue and working to have this functioning as expected for all workflows once more. This issue is only impacting Workflows, and we have confirmed Journey events are processing as expected.
We'll continue to provide updates here as we learn more.
May 2, 08:01 PDT