Quick recovery checklist
- Do not repeat the Carryover action after an indeterminate result.
- Refresh both the source and destination boards.
- Check the item’s exact destination, mapped text values, and updates.
- Inspect monday’s native Activity Log and Undo option where available.
- Record the Carryover reason code, UTC time, and app version before closing the result.
What each outcome means
| Carryover state | What to do |
|---|---|
| Blocked before move | Fix the named access, mapping, hierarchy, or data issue and run a fresh safety check. |
| Move stopped | The command stopped before it could safely dispatch. Refresh native state before starting over. |
| Move indeterminate | Do not retry. Inspect both boards and the Activity Log; contact support if the outcome remains unclear. |
| Verification failed | Inspect the mismatched destination field and use native Undo if appropriate. |
| Move verified, receipt uncertain | Do not repeat the receipt write. Inspect destination updates and preserve the local fallback shown by Carryover. |
| Handoff verified | Review the native receipt and share the destination item with the receiving team. |
What to send support
Helpful and safe: stable reason code, UTC time, app version, whether you inspected both boards, and a concise description with customer names removed.
Do not send: passwords, access tokens, API keys, client secrets, cookies, full URLs with parameters, raw board exports, copied activity logs, or screenshots containing unrelated items.
If content is sent accidentally, access will be restricted and the content will be removed from the support case as soon as the issue allows.
Report a security or privacy concern
A security or privacy incident receives the highest support priority.
Use the support address with the subject Carryover security. For suspected secret exposure, cross-account access, an unauthorized mutation, or content exfiltration, stop using the affected action and preserve only content-free facts. Carryover’s move and receipt switches can be disabled independently while the incident is investigated.
Initial response targets
These are public-preview operating targets, not an uptime service-level agreement.
- Suspected unauthorized mutation, security, or privacy incident: same-day acknowledgement when received.
- Indeterminate move or receipt: one business day.
- Blocked workflow, documentation, or general question: two business days.
Support does not bypass a product blocker or test a repair against customer data without explicit authorization.