We are setting disposition codes in Architect v2.6 using the SetDisposition block. The flow completes successfully, and logs show Disposition Code Satisfied. However, the Conversation Event API query returns null for properties.dispositionCode. We need this field populated for workforce reporting. Environment is AWS US-East-1.
Check the end node configuration. Sometimes the flow ends before the disposition is committed to the event store. Try moving SetDisposition right before the End block and ensure no routing logic follows it. Also verify the property name matches exactly.
Moved the block to the immediate end node. Verified the API response now includes the property. Thanks for the tip on the execution timing.
While the End node fix works, using a Data Action to write directly to conversation properties can be more robust for complex routing scenarios. The SetDisposition block is convenient but limited by flow version constraints. A POST to /api/v2/conversations/{conversationId}/properties allows explicit control over the payload structure.