h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

This node operation allows an administrator to stop a specific user job that is currently running on the server. It is useful in scenarios where a job needs to be forcibly terminated, for example, if it is stuck, consuming excessive resources, or no longer needed. This operation provides control over active jobs at the administrative level.

Practical examples:

  • An admin notices a long-running data import job that is causing performance issues and wants to cancel it.
  • Stopping a batch processing job that was started by mistake or with incorrect parameters.
  • Managing server load by terminating unnecessary or stalled jobs.

Properties

Name Meaning
Job ID The unique identifier of the job to be stopped

Output

The output will contain the full HTTP response from the server after attempting to cancel the specified job. This typically includes status information about whether the cancellation was successful or if there were any errors.

The json output field will reflect the server's response body, which may include confirmation details or error messages related to the job cancellation request.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication to the server.
  • The node makes a POST request to the endpoint /user_jobs/{job_id}/cancel where {job_id} is the provided job identifier.
  • Proper permissions are required to perform administrative actions such as cancelling user jobs.

Troubleshooting

  • Invalid Job ID: If the job ID does not exist or is invalid, the server will likely return an error indicating the job was not found. Verify the job ID before attempting cancellation.
  • Insufficient Permissions: Attempting to cancel a job without administrative privileges will result in an authorization error. Ensure the API key used has the necessary admin rights.
  • Job Already Completed or Cancelled: Trying to cancel a job that is no longer running may return an error or a message indicating the job cannot be cancelled.
  • Network Issues: Connectivity problems can cause the request to fail. Check network settings and server availability.

Links and References

  • Refer to your server's API documentation for detailed information on job management endpoints.
  • Consult your platform's admin guide for managing user jobs and permissions.

Discussion