Problem

Users receive an unclear 403 error when calling the rich-parameters API endpoint for organizations that don't have any provisioners running:

{
  "message": "Job hasn't completed!"
}

This error message is confusing and doesn't provide actionable guidance to resolve the issue.

Expected Behavior

The API should return a more descriptive error message that:

1. Clearly explains that no provisioners are available for the organization
2. Provides actionable steps to resolve the issue
3. Uses an appropriate HTTP status code

Steps to Reproduce

1. Ensure the target organization has no running provisioners
2. Make a request to the rich-parameters API endpoint
3. Observe the unhelpful 403 error response

Impact

• Poor user experience due to unclear error messaging
• Increased support burden as users don't understand how to resolve the issue
• Time wasted troubleshooting when the solution is straightforward

Additional Context

This affects non-default organizations specifically where provisioner setup may not be automatic or obvious to end users.