Sent without persisted mapping
If creation cannot be established, retain an unresolved case and query via external references/profile. Do not change keys to recreate work.
TRUSTED FACTORYFLOW
Connect the right interface. Preserve accountability.
From execution to vendor jobs/missions: mapping, identity, states and recovery at equipment boundaries.
Adapters translate protocols, not every authority.
Two sides have distinct identities and states
FactoryFlow supplies authorized intent and execution IDs. Vendor systems receive jobs, missions or commands under their interface, mode and authentication. A FactoryFlow user token is not automatically robot-control authority. Adapters retain mappings before resubmission to recognize existing work.
Fleet/RCS may own scheduling and traffic; cells/controllers retain programs/motion. Mapped states preserve native codes and timestamps for investigation. Selected WMS/MES systems retain business confirmation.
An execution must lead back to vendor work.
| Reference | Example | Purpose |
|---|---|---|
| executionId | EXE-010 | Link to source task and demand |
| vendorMissionId | MSN-010 | Query after a lost response |
| adapterProfileVersion | DEMO-PROFILE-R1 | Identify mapping and gates used |
| sourceState / occurredAt | Native state / source timestamp | Distinguish stale callbacks |
| correlationId | Journey-wide, distinct from eventId | Investigate across domains |
Three cases to design before retry.
ACK without completion
Observe actual state and contract-defined waits; on source loss assign authorized verification. ACK cannot close tasks or ledgers.
Reconnect and stale callbacks
Read sourced snapshots, order-check and deduplicate. Contradictory states require reconciliation, not automatic last-arrival wins.
Physical handover belongs in acceptance.
Test selected model, firmware, mode and options: occupied stations, cancellation during execution, connection loss and recovery. Compare software outcomes with field observations and business ownership.