You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create overflow calendar. With all of these different resources available we may want 2 new leadmo accounts: Woxom AI (for all of the "golden" workflows and overflow calendar) and Woxom AI Testing (for creating users and appointments in the tuner app). With this scheme, we can make changes to the workflow in the Woxom AI Testing account and run thousands of automated tests against the resources in that account, and once the workflow is smoke-tested, we can copy it over to the Woxom AI account (and then clone it to the others). This gives us the flexibility of having a "stable" workflow (for restoring broken pipelines in other accounts) and a "development" workflow (for feature development). (edited)
Possible Solution
Once calendar is created, make any calls to book an appointment that fail, instead try again against the shared calendar.
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
Create overflow calendar. With all of these different resources available we may want 2 new leadmo accounts: Woxom AI (for all of the "golden" workflows and overflow calendar) and Woxom AI Testing (for creating users and appointments in the tuner app). With this scheme, we can make changes to the workflow in the Woxom AI Testing account and run thousands of automated tests against the resources in that account, and once the workflow is smoke-tested, we can copy it over to the Woxom AI account (and then clone it to the others). This gives us the flexibility of having a "stable" workflow (for restoring broken pipelines in other accounts) and a "development" workflow (for feature development). (edited)
Possible Solution
Once calendar is created, make any calls to book an appointment that fail, instead try again against the shared calendar.
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: