Document ServiceControl headers

nservicebus/messaging/headers.md

@@ -486,3 +486,52 @@ snippet: HeaderWriterDataBusConvention
 #### Example body
 
 snippet: HeaderWriterDataBusConventionBody
+
+## ServiceControl
+
+### ServiceControl.RetryTo
+
+Value: Queue name
+
+When present in a failed message to ServiceControl, ServiceControl will send the message to this queue instead of the queue name value from [NServiceBus.FailedQ](#error-forwarding-headers-nservicebusfailedq)
+
+This is used by the ServiceControl transport adapter to bridge failed messages between different transports.
+
+### ServiceControl.TargetEndpointAddress
+
+Value: Queue name
+Used by messageging bridge to return the message back to the correct queue if the failed message reach
+
+### ServiceControl.Retry.AcknowledgementQueue
+
+Value: Queue name
+
+The queue to send an acknowledgement system message back to a specific ServiceControl queue to mark a retried message as processed.
+
+
+### ServiceControl.Retry.StagingId
+
+Value: UUID
+
+??
+
+### ServiceControl.Retry.Attempt.MessageId
+
+Value: UUID ??
+
+??
+
+### ServiceControl.Retry.Successful
+
+Contains a timestamp in the format `yyyy-MM-dd HH:mm:ss:ffffff Z` to indicate when a message was succesfully processed.
+
+Part of the control message send back to ServiceControl to signal that a message that was manually retried in ServicePulse/Control and flag as processed succesful.
+
+### ServiceControl.Retry.UniqueMessageId
+
+Contains the [NServiceBus.MessageId](#messaging-interaction-headers-nservicebusmessageid) value of the message that was succesfully processed.
+
+Part of the control message send back to
+
+
+The presence of any header key that starts with `ServiceControl.` would indicate its a message that is manually retried.