Allegro: offer publication status is confirmed more safely
Kiero OMS checks the same Allegro publication command after temporary errors and avoids reporting success when the outcome is unknown.
Allegro: offer publication status is confirmed more safely
What changed?
After a temporary Allegro 502, 503 or 504 error, Kiero OMS can check the status of the same publication command instead of immediately treating the operation as failed. A successful status read refreshes the saved offer status.
Benefit
This reduces the risk of sending the same publication again just because Allegro's response arrived too late. If the status cannot be read, the system keeps the outcome unconfirmed for a later check.
How to use it
Run offer synchronization as before and check the final publication status on the offer. After a temporary error, let the queue perform another status check. Do not create a second publication manually based only on a timeout.
Important limitations
This change does not remove Allegro errors or improve provider availability. An unknown status stays unknown until the provider confirms it. Permanent permission or data errors still require configuration changes; the feature does not add a separate durable registry of every command.