Workflow RecipesReturn to Mission ControlLocal learning progress only. No recipe action has started in this browser.
Quest log
Intermediate
Manual
Workspace access required
Agent
Investor
Wholesaler
Transaction Coordinator
Operations Lead
Handle supported Wave 2 exceptions
Recognize supported blocked, stale, ineligible, invalid, repeated, or alternative-outcome cases without forcing the normal path.Access And Alternatives
Exception handling depends on access to the affected deal, buyer, or portal record.Can I try sample data?
Focused tests cover supported exception states; no user-facing global sample is claimed.Can I do it manually?
Open the relevant native record and use only the supported blocked or alternative outcome.Can the assistant prepare it?
Conversational exception handling remains pending until server resolution can constrain the exact current step.What access is required?
An exact Wave 2 record in a supported exception state · Access to its owning workspace surfaceIs there a usage or provider dependency?
Unsupported exceptions remain unavailable instead of being simulated as complete.What if access is unavailable?
Review the current record and choose a supported manual path without forcing a mutation.Steps
Your local learning progress. This is not proof that work was completed.1 of 4: Open the exact reviewed item and identify its current exception stateNot started
- 1Open the exact reviewed item and identify its current exception state
- 2Read the blocker or caution before choosing any mutation
- 3Refresh stale evidence or choose the supported non-mutating path
- 4Record only a supported alternative outcome when the product allows it
Supported Exceptions
Stale deal readiness
Refresh the exact deal evidence and request a new readiness review before changing its stage.Supported
Incompatible deal state
Keep the transition blocked when the deal is inactive or no longer at Under Contract.Supported
Buyer ineligibility or stale shortlist
Remove the buyer from this outreach path or refresh the shortlist; do not prepare a package.Supported
Consent, suppression, or funding caution
Keep the caution visible and use the non-sending review path until the evidence is resolved.Supported
Passed buyer response
Record Passed as an explicit response without interpreting it as provider delivery or campaign attribution.Supported
Revoked, expired, or disabled portal resource
Do not create a follow-up task from invalid evidence; record the supported invalid state when appropriate.Supported
Repeated engagement
Review the deduplicated repeat count once and do not create duplicate internal tasks.Supported
No action needed
Record No action needed explicitly without pretending a task or client contact occurred.Supported
What This Teaches
- How to start this workflow without guessing the first screen.
- How to use Mission Control as the manual path.
- How to check what happened and decide whether another step is worth doing.
What Happens Next
Record outcome and review follow-up- Blocker or caution reviewed
- Unsafe mutation avoided
- Supported alternative outcome recorded
Ways To Practice
Sample pathFocused tests cover these exception states; no public global-demo exception tour is claimed.
AI helper pathPending until this helper path has enough proof.
Prerequisites
- Access to an exact deal, buyer, or portal record in a supported exception state
Readiness And Safety
Manual ready
Outcome ready
Needs evidence
- Do not add unsupported domain behavior to complete a teaching path.
- Do not bypass stale, incompatible, ineligible, suppressed, revoked, expired, or disabled states.
- Keep no-action and passed outcomes distinct from technical completion.