| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-12-18 |
error message, message id, ansible error code, schematics error code |
schematics |
{{site.data.keyword.attribute-definition-list}}
{: #handling-error}
When {{site.data.keyword.bpshort}} actions or workspace receives a non-zero return code from a command, API, UI or failed during setting up the infrastructure, by default the setup halts executing. {{site.data.keyword.bpshort}} provides resolution to handle such errors and help you get the expected behavior, output. {: shortdesc}
This is not the complete list of error messages. Some messages are created by other systems, such as IAM authentication errors messages to the {{site.data.keyword.bpshort}} action. {: note}
{: #action-errmsg}
The error messages are categorized based on the error type, error code, and error messages. The following four categories specify the type of error that you can receive. The error message indicates the reason for an error to ease to resolve. {: shortdesc}
{: #param-error}
The parameter error represents that all the required or optional {{site.data.keyword.bpshort}} actions parameters has configured with the input. {: shortdesc}
{: #param-msg}
- Action name cannot be empty.
- Action name should contain maximum of 65 character. Count character found.
- Action name should be unique. Name already exists.
- Bad Request. Error occurred while processing the Method request.
- Action ID is correct.
- The requested action cannot be located. Check that the action ID is correct and try your request again.
{: #param-resolve}
You should read the error message carefully to rectify. You can check out the required parameter is unique, has rightly provided in the payload, and you need to follow the maximum and minimum character limit to process your parameter value.
{: #svc-error}
The {{site.data.keyword.bpshort}} actions instance and resources are overloaded or down for maintenance.
{: #svc-msg}
- Internal Service Error occurred during Method request, wait a minute and try again. If you still encounter this problem contact the {{site.data.keyword.cloud}} support.
{: #svc-resolve}
- Check the user jobs and all jobs logs. For more information, see log commands
- Wait for a minute and check your configuration and execute the action again.
- Check you have the required permissions such as IAM access or key.
- Check the firewall IP are enabled.
- Check if your {{site.data.keyword.cloud_notm}} environment notification{: external} is in maintenance.
{: #state-error}
While processing the create, delete, update action, the {{site.data.keyword.bpshort}} runs the Jobs are sent to pending state. The state flow and error message depends based on the template administrator. Following are the messages you can get in the process flow.
{: #state-msg}
- Action is ready, Job cannot be executed. Check the Job status.
- Action is in queue. Wait until the action completes.
- Action is in queue. Wait until the action completes update.
- Action failed to complete. Please wait for a minute and try again.
- Action is ready for execution.
- Action is ready for execution. The configuration and settings cannot be edited.
- Action is in draft. Please add a Git repository.
- Action is ready, Job cannot be executed. Check the Job status.
- Action state could not process the request
- The requested object cannot be located. Check that the ID is correct and try your request again.
- Playbook not selected to create a Job. Please select a playbook name.
- Unable to delete the action. Action current status.
{: #state-resolve}
- Check the logs. For more information, see log commands
{: #job-error}
The {{site.data.keyword.bpshort}} jobs displays a list of jobs and their state as successful, or failed, or active (running) job.
{: #state-jobmsg}
- Job processing error.
- Unable to delete the job. Job current status.
- The Job was temporarily locked by User at Time. Please wait until any current Job execution have completed.
- Playbook not selected to create a Job. Please select a playbook name.
{: #state-jobresolve}
- Check the input configuration and settings.
- Check the job configuration timeout, if the job timeout is reached 60 minutes, the status is updated and error is returned.
You can also contact IBM support by opening a case or post a message in the Slack channel. To learn about opening an IBM support case, or about Slack channel, see Getting help and support. {: note}