Calyx Integration Hub

Bulk Upload - Troubleshoot Problems

You can view information related to the issues and solutions specific to standard user.

User Specific Issues

Table 1. Error 400
Problem Solution
You may receive following 400 error message when you try to send invalid data values for Product, Entity or Operation fields.
  • "Invalid Product supplied"
  • "Invalid Entity supplied"
  • "Invalid Operation supplied"
Verify that user is sending valid values for Product / Entity / Operation fields.
You are trying to resubmit a job and receive: "Some or all jobs ids cannot be resubmitted" 400 error message. Resubmit job is valid only for the following Sub statuses:
  • BATCH_GENERATION_FAILURE
  • BACKEND_API_NOT_AVAILABLE
  • JOB_REPORT_GENERATION_FAILURE
  • MAIL_NOTIFICATION_FAILED

Verify that the current job sub status matches with any of the above values.

When you try to search for information regarding a job ID, and you receive: "The specified information was not found" 400 error message. If Admin user, check that the job ID is valid.

If standard user, check that the job ID is valid and the user is owner of the job.

When you try to search for a job using the job ID, and you receive: "No job found with JobId <job id>" 400 error with message. If Admin user, check that the job ID is valid.

If standard user, check that the job ID is valid and the user is owner of the job.

When you try to update the status of a job, and you receive: "Current job status should be in open state" 400 error message. Check that the current job status is "OPENED".
When you try to update a job status to a status other than Aborted or Upload Completed, you may receive: "A job can only be updated to a status ABORTED or UPLOAD_COMPLETE" 400 error message. Update status API only accepts the following statuses for update:
  • UPLOAD_COMPLETE
  • ABORTED

Check that one of the above values is being supplied for Update status.

You may receive: "No File information found for Job <job id>" 400 error message when you try to update current status of a job to Upload Completed status. Check if a valid document is successfully uploaded for the job.
When you try to search for a job using the job ID, and you receive: "No job found with JobId <job id>" 400 error with message. If Admin user, then check that the job id is valid.

If standard user, then check that the job id is valid and also the user is the owner of the job.

When you try to download Failed or Success file of a job, you may receive: "failed file doesn't exist for job <job id>" / "success file doesn't exist for job <job id>" 400 error. Verify if the job status is Completed and has the required result file.
If the job status is Failed, then the results files will not be generated in case of the following sub status:
  • VALIDATION_FAILURE
  • JOB_REPORT_GENERATION_FAILURE
  • BATCH_GENERATION_FAILURE
  • BACKEND_API_NOT_AVAILABLE
When you try to download a result file of a job, you may receive: "File download is not applicable for <job status> status" 400 error. User can only download the result file when the job status is Completed.
When a Standard user try to upload a job receives 400 error. Verify that the user is the owner of the job. Standard user can only upload for the jobs that the user has created.
When you try to search for a job using the job ID, and you receive: "No job found with JobId <job id>" 400 error. Verify that the job ID is valid.
While uploading a file you may receive: "File format is not supported" 400 error. Only .csv, .xlsx and .xls files are supported.
While uploading a file, you may receive: "File size should be more then 0Mb & less then 10MB" 400 error. The supported file size should be in specified range.
While uploading a file, you may receive: "File might be corrupted, or password protected" 400 error. Verify that the file is not corrupted or password protected.
While uploading a file, you may receive: "File already exists for job <job id>" 400 error. User can only upload one file per each job.
When a Standard user try to upload a job receives 400 error. Verify that the user is the owner of the job. Standard user can only reupload for the jobs that the user has created.
When you try to search for a job using the job ID, and you receive: "No job found with JobId <job id>" 400 error. Verify that the job ID is valid.
While uploading a file, you may receive: "File format is not supported" 400 error. Only .csv, .xlsx and .xls files are supported.
While uploading a file, you may receive: "File size should be more then 0Mb & less then 10MB" 400 error. The supported file size should be in specified range.
While uploading a file, you may receive: "File might be corrupted, or password protected" 400 error. Verify that the file is not corrupted or password protected.
Table 2. Error 401
Problem Solution
You may receive 401 error message due to invalid credentials. You do not have permission to access Bulk upload APIs as you are not registered under Admin or Standard Azure Active Directory group. To resolve the issue:
  • Raise ServiceNow ticket to Dev-Ops.
  • Request for admin user/ standard user access via their respective AAD groups.
A 401 error is displayed when you try to access Resubmit Job API with user account that does not have sufficient permission to access the API. Job Resubmit is allowed only for Admin users and not standard users.
You may receive 401 error when you try to download result file for a job. Standard user can only download the result file for the jobs that the user has created.
Table 3. Error 422
Problem Solution
You may receive 422 error when you try to send invalid or incorrect input data to access Bulk upload APIs. Check that the input data is valid as per API contract.
Table 4. Error 500
Problem Solution
When you try to access any of the Bulk upload APIs with an older version of application, you may receive a 500 error message. Check that the latest migration version is being deployed in SQL Server.
User receives a 500 error - if event grid (an Azure Component manages the events) is not working properly. Check if the Event Grid is up and running.
Table 5. Error 503
Problem Solution
You may receive 503 error message when you try to access any of the Bulk upload APIs and Azure systems are not responding or stopped working. To resolve the issue:
  • Check the API Manager to make sure it is running.
  • If API Manager is running properly, check the BDL App Service, BDL Function and SQL Server to make sure it is running.
  • If API Manager is not working, send a mail to API Manager team. (or)
  • Send a mail to Team-O describing the details of the issue.
Table 6. Zero Records found
Problem Solution
When you query for a record using Job Summary API, you might get zero records in the response. If you are an Admin user:
  • Check if any jobs have been created in the last 30 days.
  • Check if filter parameter text is matching with the data in the supported columns.
  • Check if the top parameter is set to zero.
  • Check if the skip parameter value is less than the total number of jobs created in the last 30 days (x-total-count in response header).
If you are an Standard user:
  • Check if the user has created any jobs in the last 30 days.
  • Check if filter parameter text is matching with the data in the supported columns.
  • Check if the top parameter is set to zero.
  • Check if the skip parameter value is less than the total number of jobs created by the user in the last 30 days (x-total-count in response header).
User receives Zero count for any or all of the status codes. If you are an Admin user:
  • Check if any jobs have been created in the last 30 days.
  • If any of the status codes have zero count, then check that there are jobs created in the last 30 days with the matching status code.
If you are a Standard user:
  • Check if any jobs have been created by the user in the last 30 days.
  • If any of the status codes have zero count, then check if the user has created a job in last 30 days which has the matching status code.