Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

We have detected an issue that is affecting workflows that update PSA tickets. We are actively looking into the issue and will provide a solution and updates as soon as possible. We apologize for any inconvenience.

The action affected is: ConnectWise Update Service Ticket (v1). Workflows that contain this action are failing. This also affects crates that use this action, such as User Onboarding and User Offboarding V1 and V2. Once the recovery process is complete, we will re-run all failed New User Workflows.

We are pleased to inform you that the issue affecting workflows containing the ConnectWise Update Service Ticket (v1) action has been successfully resolved. Normal functionality has resumed. All services should now be operating as expected. We will now begin re-running the New User Workflows that failed today. We apologize for any inconvenience caused during this period and appreciate your patience and understanding. If you encounter any further issues or have any questions, please do not hesitate to reach out to our support team.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Forms users are reporting the inability to log in to Rewst or very long wait times for logging in.

Performance for forms-only user logins has been improved, but we are still working on permanent resolution.

We have identified an issue within our forms trigger that could potentially be the source of the intermittent login delays. A fix has been applied to address this, and we are actively monitoring the situation to ensure the effectiveness of the solution. Please report any further login delays.

This issue is also being tracked on our docs site here: https://docs.rewst.help/updates/issue-alerts

We are continuing to see some issues and are continuing to investigate

The root cause has been identified and a temporary measure has been put in place to resolve the issue. We will update further once a permanent fix has been deployed, but the platform should now be running as expected.

This issue has been successfully resolved and we are closing this alert.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

App running, engine work in progress

Failed migration from new feature deployment - we are back to normal operations. We were able to fix the migration issue without rolling back. The status page will update automatically when it determines we are back.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.