If a vendor commitment, vendor change or vendor invoice doesn't post to Sage through hh2, you can send it again yourself with Retry. RedTeam Flex archives the failed copy in hh2 and sends the record again, so you don't need to open a support ticket. Retry is available for Sage 100 and Sage 300 through hh2.

Step 1: In the left menu, click Apps, then click your hh2 tile (for example, hh2-Sage300).

Step 2: Click Transactions Log.

Step 3: Find the failed record. A red icon marks it, and the Message column tells you why it failed. Once you've fixed the cause, click Retry on that row.

Step 4: Read the warning, then click Accept. If vendor invoices for this commitment were already sent to Sage, retrying a commitment disrupts their integration link.

RedTeam Flex finds the record in hh2, archives the failed copy and sends it again. This takes a few seconds. The warning closes and no confirmation message appears. The failed row is replaced by a new transaction with the status Pending.

Step 5: After a minute or two, click the Refresh button at the top of the log. When the new transaction shows Successful Post, it's in Sage. If it fails again, the Message column shows why.

If hh2 is still sending the record to Sage, RedTeam Flex stops the retry and changes nothing. You see this message:

"Unable to resend. hh2 is still exporting this record to Sage. Wait until the export finishes and check the record in hh2 before trying again. Nothing was changed."

Wait for the export to finish, check the record in hh2, then click Retry again if it still failed.

Retry doesn't replace a record that already exists in Sage. If the record is already in Sage, the new transaction can fail again (for example, with Document already exists). Check Sage first. If the record is there and you still need to send it again, delete it in Sage, as the warning in Step 4 explains, then click Retry. If it isn't in Sage and Retry keeps failing, contact RedTeam Support with the transaction number.