When an AI Agent updates a Contact Field (e.g. $contact.specific_start_time) and triggers a "Make HTTP Request" action referencing that same field within the same conversational turn, the HTTP request sends the stale/previous value instead of the newly updated one.

The HTTP Request action should use the latest, persisted value of a Contact Field — even when that field was updated earlier in the same turn — so sequential workflows (update field → call external API with that field) produce consistent, accurate data.

Within a single AI Agent turn, actions run using a snapshot of the contact's data taken at the start of that turn. If a Contact Field is updated and then referenced by an HTTP Request within that same turn, the request will use the value the field had before the update, not the new one — because the update hasn't been reflected in that turn's snapshot yet.