> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/~/revisions/oox5xThRKRJizwPMPxvl/updates/issue-alerts.md).

# Alerts

## 2025

<details>

<summary>⚠️ Resolved: Service performance issue - US region October 8th, 2025</summary>

On October 8, 2025, following a routine platform deployment, our US region experienced degraded performance affecting workflow execution speeds. From 10:30 AM EDT to 12:31 PM EDT, customers may have noticed slower task completion times and some webhook timeouts.

During this platform update, we introduced an enhancement to improve task log storage by writing data to cloud storage in addition to the existing database storage method. However, the new implementation opened a new AWS connection for each task log operation instead of reusing existing connections. This led to excessive resource use on our workflow processing servers and temporary performance degradation.\
\
Our engineering team identified the issue within approximately 30 minutes of the update’s completion and deployed a fix. Service was fully restored by 12:31 PM EDT. It's recommended that all customers verify that tasks executed in their workflows executed as expected during this degradation window.\
\
We apologize for any inconvenience this incident caused. We take platform stability seriously and are committed to learning from this incident to provide you with more reliable service. The swift detection and resolution demonstrates our team's ability to respond quickly to issues, and the improvements we're implementing will help prevent similar issues in the future.&#x20;

#### Updates

You can monitor live updates and service status at: <https://status.rewst.io/>

#### Need help?

Rewst support is always available here: <https://discord.gg/rewst>

#### Create a ticket

[Email the team](mailto:roc@rewst.io)  and someone will be in touch ASAP.

</details>

<details>

<summary>⚠️ Upcoming: Planned maintenance window - US region August 9th, 2025</summary>

On Saturday, August 9th, at 11:45 PM EDT, Rewst will be performing performing brief maintenance on the US instance [app.rewst.io](http://app.rewst.io/). Our engineering team will be conducting work involving database connection management to ensure continued platform stability and performance. During this brief window, the Rewst platform, including the user interface, API access, and workflow execution, will be temporarily unavailable. The duration of this work outage will be approximately five minutes. Normal operation will resume immediately after the work is complete. We believe that disruption will be minimal, but recommend that you monitor for failed workflows after the maintenance is conducted, and rerun workflows as needed.&#x20;

#### Updates

You can monitor live updates and service status at: <https://status.rewst.io/>

#### Need help?

Rewst support is always available here: <https://discord.gg/rewst>

#### Create a ticket

[Email the team](mailto:roc@rewst.io)  and someone will be in touch ASAP.

</details>

<details>

<summary>⚠️ Upcoming: Planned maintenance window - All Regions June 19th, 2025</summary>

On Saturday, July 19th, the Rewst engineering team will be performing regional critical PostgreSQL upgrades and infrastructure enhancements. The Rewst platform—including the user interface, API access, and all workflow execution—may be intermittently unavailable during the maintenance window. While the duration may be as little as 15 minutes, there is potential for it to last as much as two hours. Our team will work to minimize service disruption in each region. We recommend rescheduling any critical automations during those periods. Please check your region's maintenance time window in the list below. While we'll try to minimize disruptions, we do recommend rescheduling any critical automations during that period.

The maintenance is scheduled across multiple regions during off-hours as follows:<br>

* US Instance:
  * Date: Saturday, July 19, 2025 10:00 PM – Sunday, July 20, 2025 12:00 AM EDT
  * Sunday, July 20, 2025 02:00 – 04:00 UTC
* UK Instance:
  * Date: Saturday, July 19, 2025 2:00 AM – 4:00 AM BST
  * Saturday, July 19, 2025 01:00 – 03:00 UTC
* EU Instance:
  * Date: Saturday, July 19, 2025 3:00 AM – 5:00 AM CEST
  * Saturday, July 19, 2025 01:00 – 03:00 UTC
* AU Instance:
  * Date: Sunday, July 20, 2025 2:00 AM – 4:00 AM AEST
  * Saturday, July 19, 2025 16:00 – 18:00 UTC

#### Updates

You can monitor live updates and service status at: <https://status.rewst.io/>

#### Need help?

Rewst support is always available here: <https://discord.gg/rewst>

#### Create a ticket

[Email the team](mailto:roc@rewst.io)  and someone will be in touch ASAP.

</details>

<details>

<summary>⚠️ Resolved: Performance degradation due to memory exhaustion - US region June 6th, 2025</summary>

On June 6, 2025, from 8:15 AM to 10:00 AM EDT, we detected that workflow processing in Rewst was experiencing significant delays in the US region. The issue has since been resolved, and workflows are now processing normally.&#x20;

We appreciate your patience as we continue to strengthen our systems. Our team has taken steps to improve monitoring and infrastructure responsiveness to help prevent similar incidents across all regions in the future.

#### Updates

For ongoing status updates, please visit: <https://status.rewst.io/>

#### Need Help?

Rewst support is always available here: <https://discord.gg/rewst>

#### Create a Ticket

[Email the team](mailto:roc@rewst.io)  and someone will be in touch ASAP.

</details>

<details>

<summary>⚠️ Issues with Sherweb service provider API - April 15th, 2025</summary>

We are currently experiencing issues with the Sherweb Service Provider API, which is impacting functionality in Sherweb-related integrations. Our team is in active communication with Sherweb to better understand the root cause and work toward a resolution. We'll provide updates as more information becomes available.

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [Email the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Issues with workflow processing - April 11th, 2025</summary>

On April 11 at 1:30 ET, we detected some functionalities within Rewst are currently impaired. Users are experiencing issues related to multi-level default values not properly populating. This is primarily being experienced with certain ITGlue functionalities. We have identified a fix and are rolling it out on a region-by-region basis.

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [Email the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Resolved: Integration authentication failures - April 9th, 2025</summary>

On April 9th, Our monitoring system detected that authentication for some integrations in Rewst are experiencing failures. We are currently investigating the issue and will provide more information as soon as it is available.

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [Email the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Resolved: Interrupted workflow execution in US instance - April 4th, 2025</summary>

On April 4, Rewst identified an issue that interrupted workflow execution in the US instance from 2:30 PM EDT to 2:45 PM EDT. Running workflows may have been interrupted and may need to be restarted.&#x20;

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [Email the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Resolved: Service degradation in US instance - April 3rd, 2025</summary>

As of April 3, 2025 at 5:00 PM EDT, Rewst has identified an issue that is causing service degradation in the US instance. We are actively working to resolve the issue. We will update you when a permanent fix is implemented.

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ New Crates available with old Crate deprecation - March 26th, 2025</summary>

We're thrilled to announce the launch of four new crates in the Crate Marketplace:

* Microsoft: User Onboarding
* Google: User Onboarding
* Microsoft: User Offboarding
* Google: User Offboarding

These new crates come with the latest features and enhancements to make your user onboarding and user offboarding processes smoother and more efficient. **The following crates will no longer be available in the Crate Marketplace as of April 4, 2025**:

* Rewst: User Onboarding
* User Offboarding v2
* User Offboarding Crate

While these crates will still function, they will not receive any additional feature enhancements. We recommend migrating to the new crates listed above to take advantage of the latest updates.\
For crate migration assistance, please reference the [Migrate between Crate versions](/~/revisions/oox5xThRKRJizwPMPxvl/documentation/crates/migrating-between-crate-versions.md) and [Crate deprecation FAQ](/~/revisions/oox5xThRKRJizwPMPxvl/documentation/crates/crate-deprecation-faq.md).

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ App Builder incorrectly displays HTML containers - March 14th, 2025</summary>

On Friday, March 14th, some Rewst users experienced disruptions with App Builder where their HTML containers were not displaying correctly. The issue has been identified and a resolution has been implemented.&#x20;

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Routine system maintenance - March 8th, 2025</summary>

We will be performing maintenance on: **Saturday**, **March 8th, 2025 from 1000 - 1300 EST (1500 – 1800 UTC).**

You may experience periodic service interruptions during the maintenance window across all regions.

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Routine system maintenance for UK - March 7th / March 8th, 2025</summary>

We will be performing maintenance on:\
**March 7th, 2025** 2100–2300 EST / March 8th, 2025 0200–0400 UTC

No outages or end user impacts are expected. Thank you for your understanding.&#x20;

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Routine system maintenance - February 8th and 15th, 2025</summary>

We will be performing maintenance on:\
**Saturday**, February 8th, 2025 from 2:00PM – 4:00PM EST (19:00–21:00 UTC)\
**Saturday**, February 15th, 2025 from 2:00PM – 4:00PM EST (19:00–21:00 UTC)

Please note: You may experience periodic service interruptions during the maintenance windows for instances hosted in the US region.

If you have any urgent concerns, please contact your support team.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Transition to OAuth 2.0 authentication for Pax8 APIs - January 7th, 2025</summary>

As of **January 31st, 2025**, Pax8 will retire API Key requests as a method of authentication. To ensure uninterrupted access to the Pax8 integration, Rewst customers are required to transition to OAuth 2.0 for API authentication.

To continue using the Pax8 integration with Rewst, you will need to transition to OAuth 2.0 authentication before January 31st, 2025. For information on how to update the configuration in Rewst, check this page: [Broken mention](broken://pages/JTewUNxCZGcGg3FdP57W)

This transition to OAuth 2.0 provides enhanced security, streamlined user experience, and improved API access management.&#x20;

If you have any questions or need assistance with the transition, our team is here to help.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

## 2024

<details>

<summary>⚠️ Upgrade to V4 of ConnectSecure needed by December 31st, 2024</summary>

We’re excited to share an important update regarding your ConnectSecure integrations (formerly CyberCNS). To enhance functionality and ensure seamless performance, we’ve developed a new V4 version of the ConnectSecure integration. This update is designed to provide improved capabilities and long-term support as we transition from the V3 integration, which will reach its end-of-life on December 31st, 2024.

While the migration to V4 requires a few configuration steps, we’ve made the process straightforward. Simply reach out to your ConnectSecure representative or log in to your ConnectSecure instance to obtain your V4 credentials and hostname. Please note that related endpoints in your existing generic actions will also need to be updated to the new URLs.

To make the transition as smooth as possible, we’ve created detailed migration documentation, which you can find here: <https://docs.rewst.help/documentation/integrations/security/cybercns/connectsecure-integration-migration-v3-to-v4>.

We’re here to support you every step of the way. If you have any questions or need assistance, don’t hesitate to reach out to our team.Thank you for partnering with Rewst as we continue to enhance your experience with ConnectSecure!

</details>

<details>

<summary>⚠️ Resolved: App Builder domains not provisioned in UK - November 13th, 2024</summary>

### Issue Resolved

**Date**: Friday, November 13th, 2024\
**Time**: 7:38 PM EDT

We were performing upgrades across all Rewst instances to how we provision domains for live sites. The upgrades were successful in all of our instances, but failed in prod US at 6:33 PM EST. We were troubleshooting for 50 minutes and managed to roll back at 7:23PM bringing rew\.st domains back up. There was additional work needed to get custom domains back, which was completed at 7:38PM.

### Issue Identified

**Date**: Friday, November 13th, 2024\
**Time**: 6:33 PM EDT

App Builder domains were not being provisioned in UK leading to live sites not being available.&#x20;

### **Updates**&#x20;

For the latest information, please refer to <https://status.rewst.io/>

Please contact our support team if you have any questions or need further assistance.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Resolved: Platform disruption to workflow processes for US customers - November 6th, 2024</summary>

**Date:** Wednesday, November 6th, 2024

**Time:** 10:53 AM - 11:40AM EST

On November 6, 2024, from 10:53 AM EST to 11:40 AM EST, an unintended disruption occurred in our production environment, impacting workflow processing for our US customers. While working towards a resolution, there were failures of workflows running at the time. This temporarily affected real-time processing across parts of our application. The issue was resolved and workflows are running as normal.&#x20;

Thank you for your understanding as we work to strengthen our safeguards. We are committed to maintaining the reliability and resilience of our platform and will continue to enhance our processes to prevent such incidents in the future.

**Updates**&#x20;

For the latest information, please refer to <https://status.rewst.io/>

Please contact our support team if you have any questions or need further assistance.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Resolved: Rewst experiencing performance degradation for US Region - November 1st, 2024</summary>

### Issue Resolved

**Date**: Friday, November 1st, 2024\
**Time**: 4:30 PM EDT

After further investigation, it was discovered that a previous settings change intended to improve performance was causing timeouts because of the large number of connections in the environment. Upon reverting the setting, performance returned back to normal around 4:30PM EDT.

### Issue Identified

**Date:** Friday, November 1st, 2024

**Time:** 11:58 AM EST

ReOn Friday, November 1, 2024 beginning at 10:23AM EDT, the workflow engine began exhibiting slow performance while executing tasks. Our platform team was alerted when the pending task queue grew out of normal boundaries and began investigating the problem.

### Updates

**Time:** 2:00 PM EST\
\
Investigation showed that increasing the number of worker nodes had an adverse affect on workflow processing, pointing to a potential issue with the message queue system experiencing timeouts. To stabilize the task queues, the team adjusted the number of worker nodes until processing normalized, while continuing to troubleshoot the root cause. By 2PM EDT, the task processing rate was normalized, although still slower than normal.

For the latest information, please refer to <https://status.rewst.io/>

Please contact our support team if you have any questions or need further assistance.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️ Resolved: Workflows failing to execute in app.rewst.eu - October 31st, 2024</summary>

**Date:** Thursday, October 31st, 2024

**Time:** 8:20 UTC / 4:20 AM EDT

October 31st, 2024 at 8:20 UTC Rewst discovered an issue with workflow executions initializing in the European instance. UK Customers were not affected. This was escalated internally for review per the standard process. Rewst traced the issue to a partition issue. This issue was fixed and Rewst is currently operating as normal while we work to publish a long-term fix to ensure this doesn't happen again.

**Updates**&#x20;

For the latest information, please refer to <https://status.rewst.io/>

Please contact our support team if you have any questions or need further assistance.

* **Discord** - The ROC is always available here: <https://discord.gg/rewst>
* **Create a Ticket** - [E-mail the team](mailto:roc@rewst.io) and someone will be in touch ASAP!

</details>

<details>

<summary>⚠️  Routine system maintenance -October 26, 2024</summary>

**Date:** Saturday, October 26, 2024

**Time:** 3PM to 3:30PM ET

During this period, the system will remain online; however, you may experience temporary performance degradation, such as slower response times. We appreciate your understanding as we work to enhance the performance and reliability of our platform. If you have any concerns or experience significant issues, please reach out to our support team or your CSM.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rewst.help/~/revisions/oox5xThRKRJizwPMPxvl/updates/issue-alerts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
