When you edit a queue in the IllyVoIP app, the update uses the queue revision that the app loaded. If another administrator changes the queue first, the service can reject your stale update. Reload and compare the latest settings before submitting again.
These steps follow the Android app in version 1.0.46, build 272. Use your own account and the permissions assigned to it; other installed releases can have different controls.
1. Open the correct queue and review its current state
- Open the queue management area and select the intended queue.
- Check its name and current settings before entering edit mode.
- Confirm that your role permits the change and read any readiness notice.
- Coordinate with other administrators if the queue is actively being configured.
A visible queue is not proof that all update operations are available. Readiness and permission checks can restrict mutation while still allowing a view. Do not attempt to bypass a disabled control with an older screen or a direct request.
2. Record the intended edit
Before changing several fields, note the current values and the specific replacements you intend to make. Keep this note private and exclude customer information. It is especially useful if another editor may be working on the same queue or the app needs to refresh after a conflict.
- Change only the settings required for the task.
- Read the help text and validation for each offered control.
- If replacing hold music, complete the required upload workflow before saving.
- Review all visible pending values together rather than assuming only the last touched field will be submitted.
Queue settings, queue membership and incoming-number routing are related but separate workflows. Changing a queue setting does not automatically prove that an agent was added or that a number now targets the queue. Verify those outcomes in their appropriate views when they are part of your intended change.
3. Save once and inspect the result
- Submit the update and wait for completion.
- Read any returned validation or readiness message.
- After success, reopen or refresh the queue and confirm the intended values.
- If connectivity is interrupted, inspect the current saved queue before repeating the action.
The app expects a usable updated revision after a successful settings update. If the result cannot be established, do not treat the presence of your typed values on screen as proof that the server saved them. Reconcile with the current queue state.
4. Handle a concurrent-change conflict
A queue revision conflict means the version you edited is no longer current. In the reviewed app, that conflict triggers a refresh of the queue. The refreshed fields can replace your unsaved local values, which is why retaining a short note of your intended change matters.
- Read the conflict message and let the current queue load.
- Compare the latest saved values with your note.
- Identify any change another administrator made and preserve it unless you have an explicit reason to alter it.
- Reapply only the still-needed part of your original edit to the refreshed version.
- Review the full settings again and submit once.
Do not keep pressing Save against a stale screen or restore every old value to make the warning disappear. If the changes conflict in purpose, coordinate with the other administrator before making another update. A new revision is a concurrency safeguard, not an error to work around.
5. Verify the practical effect
Confirm that the settings displayed after refresh match the agreed configuration. If the change affects waiting callers, music or queue behavior, arrange an authorized test that does not disrupt customer traffic. A successful settings save does not verify the audio file’s perceived quality or every runtime path.
If the update still cannot be completed
Record the queue reference, approximate time, intended fields and exact sanitized message. Distinguish a revision conflict from a missing permission, incomplete upload or service-readiness restriction. Send that focused information to Support; do not include SIP passwords, authentication tokens or complete customer-call details.
Related guides
Reviewed 12 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.