Troubleshooting an Update That Shows Not Available

Troubleshooting an Update That Shows Not Available starts by identifying which QCUL stage or safety gate is actually failing; the fix should address that layer rather than bypassing the protection.

Likely causes

  • Joomla supplied metadata but QCUL cannot safely select the row for the current lab state.
  • The target may already be installed in the lab, previously tested, or lack usable package metadata.

Troubleshooting procedure

  1. Read Live Site, Laboratory, and New Version columns.
  2. Look for Already installed in lab/Tested here status.
  3. Refresh update metadata.
  4. Do not force a package into QCUL outside the supported update workflow.

Verify before production

After resolving Troubleshooting an Update That Shows Not Available, the selected update should return to a clear testable/completed state with exact package/version evidence. Open the lab and report again; do not proceed to production while the test remains failed, ambiguous, or based on a damaged/stale laboratory state.

Capture evidence before changing more things

While troubleshooting Troubleshooting an Update That Shows Not Available, preserve the exact displayed state/error and relevant report/task/log evidence before reinstalling, refreshing, removing, or manually editing data. QCUL’s state machine is designed to make failed work diagnosable; changing several layers at once can erase the evidence that identifies the real cause.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.