Callout Errors

There are several errors, mostly due to multi-user interaction, which can occur in the Callout Module . The state of the callout can change as a result of another user's action, or as a result of the flow of the callout itself (going to Wait or Done status). For example, if one user has stopped, resubmitted, or closed a callout that you are trying to edit, you will receive an error. In most all situations, the errors are caused by having stale data on the page, so clicking the Refresh button on the bottom of the Callout Definition table resolves the error. The following is a list of the most common errors you may see and what causes them.

Error	Explanation
3452 raiseErr('CO '||j.co_id||' already exists for '||namefromid(a_classId(i),2) )	Adding a new sub-callout, but another user already added that class as a sub-callout.
raiseErr('Invalid status for update list chain: '||namefromid(i.status,14)); raiseErr('Invalid current attempt for update list chain: '||i.curr_att);	Update list chain means checking or unchecking the "chain" checkbox in the sub-callout section.
raiseErr('Invalid status for updateCo: '||a_co(i)||' '||namefromid(j.status,14)); raiseErr('Invalid current attempt for updateCo: '||a_co(i)||' '||j.curr_att);	UpdateCo is the routine for saving any of the sub-callout section data - while the sub-callout is in new/edit status.
raiseErr('Quantity must be at least '||cnt||' for: '||a_co(i));	If you have tried to set the quantity selector to something less than the current number of accepts + beingCalled.
ret_msg :=  'Invalid status for initiating CO: '||a_co(i)||' '||namefromid(j.status,14)||'.'||chr(10)|| 'Another user may have modified the callout.'; ret_msg :=  'Invalid curr_att for initiating CO: '||a_co(i)||' '||j.curr_att||'.'||chr(10)|| 'Another user may have modified the callout.';	While trying to initiate a callout (from the Manual Bypass section) 0 if another user submitted it or closed it.
raiseErr('Invalid current attempt. (You need to refresh...)');	When using any of the Action buttons in the sub-callout section - ARCOS verifies that your page "knows" the true current attempt.
ret_msg := 'Invalid action for this callout. (You Need to refresh...)'	The sub-callout may no longer be in a status for which the desired action is valid. For instance, the user may click the Pause button, thinking the callout is running. But if the callout has actually already gone to Wait status, Pause is no longer valid.
raiseErr('You can only reopen a Closed callout.');	With the new Reopen button, another user may have already reopened it.
raiseErr('No COs found to Stop!');	When using the Stop button in the top/main section of the page, if there is only one sub-callout and it just went to Done status, the callout is no longer"'stoppable."
raiseErr('Callout could not be closed');	When using the Close button in the top/main section of the page, if another user resubmitted a callout which was in Stop status.
raiseErr('Cannot delete - there are subcallouts!');	Delete button (in top section). Your page thinks there are no subcallouts but another user just added a sub-callout.
ret_msg := 'Quantity currently cannot be < '||cnt||'.';	When using the Edit Quantity action button and you change the quantity lower than the allowable quantity.

---

*Note: Not all companies have all of the items described in the Online Help.

*Please note, the ARCOS online documentation is a living document that is always under review. If you see information that is inconsistent with the behavior in the application, or you do not see a page covering an ARCOS feature you would like to know more about, please contact the ARCOS Support Center.