The TextBase builder jobs in Flow sometimes fail with the error "Error when trying to submit the job to MultiTrans: TextBase is Offline."

The batch of files also has the job ID of MultiTrans Job Id: -1

1. Upgrade Flow

Version 7.0.24067.1 of Flow added 2 new settings under "System Parameters > Miscellaneous" which prevent this issue from occurring:

1. "The maximum number of attempts to establish an online connection with the Textbase" (default value = 10)
2. "Maximum waiting time between each retry to get Textbase online (In Seconds)" (default value = 1 sec)

If the you still see the "Textbase is Offline" error with the default settings, try increasing the waiting time between each retry to 60 seconds and then reschedule the job using the 'clock' icon on the History tab:

Upgrade to the latest version if you are still using an earlier version.

2. Make sure the TextBase is online

Check whether the target TextBase is online in the Administration Console. If it is offline (indicated by a gray circle), select the TextBase and click "Put Online":


If the TextBase was offline, re-run the TextBase Builder job in Flow once the TextBase is back online. Otherwise if the TextBase was already online, see the workaround steps below to manually reschedule the failed uploads.

Workaround: manually reschedule uploads

This workaround is only necessary in versions of Flow below version 7.0.24067.1. Upgrade to the latest version of Flow to prevent this issue from occurring.

Next to each file that has failed to be uploaded to its target TextBase, you can click the red cross icon to reschedule that file:

Then select the TextBase Builder tab and you'll see a new TextBase Update job ready to upload the file that you rescheduled. You can click the green play button to run this job immediately (note: TextBases are temporarily taken offline when appending new files to them, so only do this during a quiet period):


Repeat this for each file that has failed. Files on the History tab are sometimes split up into several batches. You can reschedule all the files in the same batch to be uploaded at the same time by rescheduling each file in that batch one by one. In the example below, you can reschedule each of the files in Batch 1 together OR the single file in Batch 2, but do not reschedule both Batch 1 AND Batch 2 in the same TextBase Update job:

Example of a TextBase Update job containing only the failed files from "Batch 1" from the screenshot above:

 

A TextBase Update job groups files into 'batches' based on the document's import options and the target TextBase (i.e. which TextBase the file is being appended to). There can be multiple 'batches' of files that target the same TextBase but the documents used different import options, so these documents are uploaded in a separate batch.

When multiple batches target the same TextBase, the first batch will typically succeed but any subsequent batches for that same TextBase will fail because the TextBase is still offline from processing the first batch.