Table of contents
Appifio Creator · Lesson AS16 · Intermediate · Aura series · MCP
IDE ↔ Creator conflicts
& expired tokens
& expired tokens
When several people edit: who clicks Save changes last; what to do when a token expires - clear and safe.
Learning goals: Avoid overwriting each other; renew/revoke tokens; know when to open X09/X13.
Previous: AS14-AS15 · Next: AS17 · ~12 minutes
Save changes Current Changes Revoke Create token
1. Conflict map
Person A edits in the IDE (sandbox)
Person B edits in Creator (Changes draft)
→ Whoever clicks Save changes last in Creator decides what visitors see
Team rule: one person “locks live” each time · announce before Save
2. Glossary
| Term | Meaning | Where you see it |
|---|---|---|
| Conflict | Two sides edit at once - easy to lose the other’s work | Team practice |
| Expired / rejected token | IDE no longer has permission to connect | IDE / MCP tab |
3. Safe practice
- Agree who may edit in the IDE right now, and who may edit in Creator.
- Before Save changes: compare Changes vs Current; use Versions / Clone if you need to keep the old copy (E01, K02).
- Token expired or permission error: MCP tab → Revoke (if needed) → Create / resume session → Create token → update the IDE (X09).
- Suspect a leaked token: Revoke immediately - don’t “try a bit more first.”
4. Comparisons
- Google Docs: many people edit at once - Appifio live needs a more deliberate Save changes rhythm.
- Git merge conflict: same idea - two edited copies collide.
5. Common issues
| Situation | Fix |
|---|---|
| Lost a Creator edit you just made | Check Versions / History; realign the process (X13) |
| IDE edited but visitors don’t see it | Normal - someone must Save changes in Creator |
6. Checklist
- Does the team have a “who Saves live” rule?
- Do you know Revoke + create a new token?
AS17 - Aura webapp handoff checklist
Internal navigation (same language)
Appifio Creator · Aura series · AS16
