Skip to content

Commit c252676

Browse files
NovaBrangitbook-bot
authored andcommitted
DocsUpdate-1394: Crate Release and Old Crate Deprecation Alert
1 parent 2654372 commit c252676

File tree

2 files changed

+28
-39
lines changed

2 files changed

+28
-39
lines changed

prebuilt-automations/crates/crate-deprecation-faq.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The ROC will continue to provide best effort support to help resolve issues with
1212

1313
<summary>Will my deprecated Crates stop working after their deprecation date?</summary>
1414

15-
No, your existing workflows using deprecated Crates will continue functioning normally. Deprecation means these Crates won't receive future updates or enhancements.
15+
Your existing workflows using deprecated Crates will continue functioning normally. Deprecation means these Crates won't receive future updates or enhancements.
1616

1717
</details>
1818

updates/issue-alerts.md

+27-38
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,33 @@
22

33
<details>
44

5+
<summary>⚠️ New Crates Available with Old Crate Deprecation March 26th, 2025</summary>
6+
7+
We're thrilled to announce the launch of four new crates in the Crate Marketplace:
8+
9+
* Microsoft: User Onboarding
10+
* Google: User Onboarding
11+
* Microsoft: User Offboarding
12+
* Google: User Offboarding
13+
14+
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**:
15+
16+
* Rewst: User Onboarding
17+
* User Offboarding v2
18+
* User Offboarding Crate
19+
20+
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.\
21+
For crate migration assistance, please reference the [migrating-between-crate-versions.md](../prebuilt-automations/crates/migrating-between-crate-versions.md "mention") and [crate-deprecation-faq.md](../prebuilt-automations/crates/crate-deprecation-faq.md "mention").
22+
23+
If you have any urgent concerns, please contact your support team.
24+
25+
* **Discord** - The ROC is always available here: [https://discord.gg/rewst](https://discord.gg/rewst)
26+
* **Create a Ticket** - [E-mail the team](mailto:[email protected]) and someone will be in touch ASAP!
27+
28+
</details>
29+
30+
<details>
31+
532
<summary>⚠️ App Builder Incorrectly Displays HTML Containers March 14th</summary>
633

734
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;
@@ -248,41 +275,3 @@ During this period, the system will remain online; however, you may experience t
248275
October 3, 2024 at 22:00 UTC Rewst was notified of slow user interface (UI) load times and reduced accessibility of the platform. This was escalated internally for review per standard process. Rewst traced the issue to a slow-running common request. This resulted in Rewst Forms and UI elements not loading for some users and reduced functionality for other users from 22:00 to 23:15 UTC. Rewst is currently operating as normal while we continue to investigate the root cause of this issue. More information will be provided as it becomes available.
249276

250277
</details>
251-
252-
<details>
253-
254-
<summary>⚠️ Update To Disable Forms (September 30th, 2024)</summary>
255-
256-
### **Issue Identified**
257-
258-
**Date**: Monday, September 30th, 2024
259-
260-
We released an update that corrected an issue where some forms marked as "disabled" were still functioning. If you had disabled form triggers within a workflow, they may now be correctly inactive. We’ve noticed a few customers were using these forms in production, and the update has properly disabled them.&#x20;
261-
262-
If you’re impacted by this change, simply re-enable the form in your trigger settings.
263-
264-
</details>
265-
266-
<details>
267-
268-
<summary>⚠️ Resolved: Lost Form Access (September 12th, 2024)</summary>
269-
270-
### **Issue Identified**
271-
272-
**Date**: Thursday, September 12, 2024\
273-
**Time**: 11:17 PM EDT
274-
275-
An update aimed at improving load times for custom forms was implemented at 3 PM EDT. This update unintentionally caused some users to lose access to forms.
276-
277-
### Issue Resolved
278-
279-
**Date**: Thursday, September 12, 2024\
280-
**Time**: 11:55 PM EDT
281-
282-
Following standard procedures, the update was rolled back, and the issue was resolved.
283-
284-
If you have any questions or concerns, please contact the ROC support team via Discord or contact your Customer Success Manager.
285-
286-
Thank you for your understanding and patience as we work to improve our platform!
287-
288-
</details>

0 commit comments

Comments
 (0)