• User ID (type of user)
• URL
• Screenshots
• Connected to NetSkope Client VPN.
• Stability of Internet Connection

• Check for the valid URL https://isca.bccl.in/
• Check for user access with VPN (NetSkope Client).
• Ensure the link is accessible.
• Check the user browser.
• Check the servers.

• In the event that a Times Group user encounters a sign-in failure, the following warning message will be displayed:
• In the event that a Sify user encounters a sign-in failure, the following warning message will be displayed:
• Check the URL from user if you can access the link (whether able to sign in or not)
• Check the DNS, SERVER, URL IP address.

• User ID (type of user)
• Screenshots
• Connected to NetSkope Client
• Browser Permissions for pop-up notification
• Stability of Internet Connection.

• Check for user access with VPN (NetSkope Client)
• Check for the user role.
• Check for the user internet connection stability.
• Ensure that the user is using a supported and up-to-date web browser.
• Check user security software, including antivirus or firewall, blocking the pop-up.

• User ID(type of user)
• Asset Name/Asset URL
• Title of asset to be updated.
• URL of asset in Tenovos
• Screenshots

• Verify the user's privilege to edit the asset.
• Verify the issue whether it is appropriate.
• Verify the asset with name and compare with screen shot
• Verify the user browser
• Verify user internet connection stability.

• Due to a lack of edit permissions, the user was unable to modify the asset's title.
• If the user wishes to edit assets, please request an update to their user role.
• Access the asset through the Content Portal and modify the title.

• Login to ISCA
• Select the asset which need to update
• Update the title by clicking on the "Edit" button beside the "Basic Asset Information" Section(marked in box):

• After editing the title, Click on "Save" button.

• After successful updating of title, Please check "Store Front" option and click on "Save" button, then it will update in tenovos.

• User ID(type of user)
• Asset Name/Asset URL
• Description of asset to be updated.
• URL of asset in Tenovos
• Screenshots

• Verify the user's privilege to edit the asset.
• Verify the issue whether it is appropriate.
• Verify the asset with name and compare with screen shot
• Verify the user browser
• Verify user internet connection stability.

• Due to a lack of edit permissions, the user was unable to modify the asset's description.
• If the user wishes to edit assets, please request an update to their user role.
• Access the asset through the Content Portal and modify the description.

• Login to ISCA
• Select the asset which need to update
• Update the description by clicking on the "Edit" button beside the "Basic Asset Information" Section(marked in box):

• After editing the description, Click on "Save" button.

• After successful updating of description, Please check "Store Front" option and click on "Save" button, then it will update in tenovos.

• User ID(type of user)
• Asset Name/Asset URL
• List of tags to be updated.
• URL of asset in Tenovos
• Screenshots

• Verify the user's privilege to edit the asset.
• Verify the issue whether it is appropriate.
• Verify the asset with name and compare with screen shot
• Verify the user browser
• Verify user internet connection stability.

• Due to a lack of edit permissions, the user was unable to modify the asset's tags.
• If the user wishes to edit assets, please request an update to their user role.
• Access the asset through the Content Portal and modify the tags.

• Login to ISCA
• Select the asset which need to update
• Update the tags by clicking on the "Edit" button beside the "tags" Section(marked in box):

• After editing the tags, Click on "Save" button.

• After successful updating of tags, Please check "Store Front" option and click on "Save" button, then it will update in tenovos.

• User ID(type of user)
• Asset Name/Asset URL
• List of tags to be updated.
• URL of asset in Tenovos
• Screenshots

• Verify the user's privilege to edit the asset.
• Verify the issue whether it is appropriate.
• Verify the asset with name and compare with screen shot
• Verify the user browser
• Verify user internet connection stability.

• Due to a lack of edit permissions, the user was unable to add the asset's tags.
• If the user wishes to edit assets, please request an add to their user role.
• Access the asset through the Content Portal and add tags to the asset

• Login to ISCA
• Select the asset which need to added
• Add the tags by clicking on the "Edit" button beside the "tags" Section(marked in box):

• After adding the tags, Click on "Save" button.

• After successful adding of tags, Please check "Store Front" option and click on "Save" button, then it will update in tenovos.

• User ID (type of user)
• Screenshots
• NetSkope Client VPN connection
• Stability of Internet Connection
• Last browser update.

• Examine the assets tab in the Content Portal to identify and address any pagination issues.
• Investigate the case

• Network Issues
• UI/UX Issue
• Pagination Logic Error
• Data Retrieval Issue

• User ID & User Name (type of user)
• Screenshots
• User's search asset title

• Verify the user network connection stability
• Verify the issue with search title given by the user.
• Verify the issue with some sample asset titles.

• Evaluate the backend processes responsible for handling search queries.
• Evaluate Indexing and Search Engine
• Data Retrieval Issue
• Search for the exact title. (Example: If searched for "Sea", all assets relevant to sea will be fetched. If searched for "Indian Ocean" only assets relevant to Indian Ocean will be fetched.)

• Login to ISCA Portal.
• Click on the Assets tab.
• Search with the asset title in the "Search box" (ex #police)

• User ID & User Name
• Screenshots
• User's search description

• Verify the user network connection stability
• Verify the issue with search title given by the user.
• Verify the issue with some sample description .

• Evaluate the backend processes responsible for handling search queries.
• Evaluate Indexing and Search Engine
• Data Retrieval Issue
• Search for the exact description. (Example: If searched for "Cricket", all assets relevant to cricket will be fetched. If searched for "2011 world cup cricket match" only assets relevant to 2011 world cup cricket match will be fetched.)

• Login to ISCA Portal.
• Click on the Assets tab.
• Search with the asset title in the "Search box" (ex #police)

• User ID & User Name (type of user)
• Screenshots
• User's search meta tags

• Verify the user network connection stability
• Verify the issue with search meta tags given by the user.
• Verify the issue with some search meta tags.

• Evaluate the backend processes responsible for handling search queries.
• Evaluate Indexing and Search Engine
• Data Retrieval Issue
• Search for the exact meta tags . (Example: If searched for "Bollywood", all assets relevant to bollywood will be fetched. If searched for "Bollywood Actor" only assets relevant to bollywood actor will be fetched.)

• Login to ISCA Portal.
• Click on the Assets tab.
• Search with the asset title in the "Search box" (ex #police)

• Screenshot of the error
• USER ID (type of user)
• Ingestion Title/assets name
• Ask URL from user.

• Verify the user has selected times content
• Verify the times content that has been previously ingestion to ISCA (Integrated Smart Content Archival)
• Check the user can be able to create ingestion in ISCA (role accessibility)
• Check the network connection.
• Check the VPN connection.
• Investigate the case

• If the user didn't have access to create ingestion, he unable to create ingestion for times content.
• In times content same ingestion cannot be created multiple times.

• Click on new ingestion

• Select the Times content from source path and valid content, also give valid schedule date and time.

• Screenshot of the error
• USER ID (type of user)
• Ingestion Title

• Verify that an ingestion with the same content has not been created previously. If a duplicate ingestion exists, you cannot create a new one.
• If the user does not have access, the following warning will be popped up:

• Enquire with the user if they possess the necessary privileges to initiate the ingestion process through manual upload.
• To determine the cause of the user's inability to create, it is essential to examine the type of data and source the user selected.
• The data size for manual assets uploads should not exceed 500MB.
• only specific formats are accepted when user attempts to create an ingestion through manual upload. (only png and jpeg format will accept)

• check with user about the format they are attempting to upload the asset in.
• check with user permissions whether he has access to create the ingestion or not. If user don't have access to create ingestion with manual upload the following error popped up :

• User should have necessary permission to create an ingestion manually.
• The Asset should be in a prescribed format for uploading.
• To create ingestion through manual upload you need to follow these steps:
  Click on new ingestion

• Select the desktop/ device from source path to upload the images manually.

• Screenshot of the error
• User role
• Need to access job details by enter the title of the job as specified by user

• Ask whether user created the ingestion successfully or not.
• Ask user to check in all tab button (where all the jobs will list)
• Ask the user whether he scheduled date and time.
• Ask the user to check network connectivity.
• Ask the user what source he selected.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• check whether the ingestion created successfully or not by entering the ingestion name which is specified by user.

• We check user can be able to list all the jobs or not
• We check user can be able to create new job or not
• we check the respective job in all tab in ingestion page.

• Screenshot of the error
• typeofuser
• Ingestion name/asset name.

• Check network connection.
• Check VPN connection.
• Investigate the case.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

1.3) Check User role and what permissions attached to that role.

• Check the ingestion created and schedule date and time given.

• Screenshot of the error
• User role

• Check network connection.
• Check VPN connection.
• Valid URL.
• Investigate the case.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• Screenshot of the error
• User role

• Check the screenshot from user
• Check for the user role.
• Ask user to Check the network connection
• Check what kind of Browser the user is using.
• Check what type of source the user selected

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• check the network connectivity
• check whether user has access to see the folders list the ingestion screen
• we check what type of source the user selected. (select the comyan source path and click on select files or folders from comyan and select the folder).

• Source dropdown is working fine with the listed folders.
• Click on new ingestion.

• Select the correct source path and click on the file or folder from comyan.

• Screenshot of the error
• User role

• We need to check from our system whether pagination is working or not, if it is working ask user to check his network connectivity, if is not working will share the issue related screenshot to respective team to fix the issue.
• ensure to check in assets tab in content portal to address the pagination issue.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• we check from our system whether the pagination is loading or not
• 3. We check in assets tab in content portal to check the pagination is loading or not

• Screenshot of the error
• User role
• Network Connection
• Ingestion Name

• Check network connection.
• Check VPN connection
• Valid URL
• Investigate the issue.
• Check the status of the job (open status, upcoming, InProgress).

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

1.3) Check Network connectivity and User permissions.

• Once the user selected the scheduled date and time then cannot be able to edit the ingestion.

• check the job whether scheduled or not here:

• check the status of the job

• Screenshot of the error
• User Id
• User role
• Check what type of source they selected.

• Check for the user role
• Check the network connection
• Check VPN connection
• Need to check whether he scheduled the job or not.
• Need to check the status of the job.
• Need to check what type of data the user selected.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

1.3) Check the network connectivity.

• check the status of the job.
• check the user scheduled the job or not
• check what type of data user selected
• we check whether ingestion successfully created or not
• user might select empty folder

• Screenshot of the error
• User role
• Network connection

• Check the error screenshot.
• Check for the user role.
• Network connection
• VPN connection
• Investigate the case

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• Screenshot of the error
• User role
• Network connection
• VPN connection
• Investigate the issue

• User trying to load Corrupted file.
• Check with the user from which source user selected the assets.
• Ask the user to check the network.
• VPN connection

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• user might load the corrupted file

• Screenshot of the error
• User role
• Asset Title

• Check the network stability from the user end.
• Verify the issue by searching with the asset title if the tags specified by the user have been added to the asset or not.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• The enter button should be selected right after adding a new tag then it will be saved.

• Screenshot of the error
• User role
• Network
• Asset name

• check the network connectivity
• Application Issue
• Check the status of the ingestion
• investigate the issue

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

1.3) Check Browser details and Network connectivity.

• access the portal and click on ingestion on the right corner there is a button review click on it and there is a option basic asset information click on it then you can edit the title or description and save it.

• Screenshot of the error
• Asset Details

• Network connection
• VPN connection
• Asset name/ ingestion name
• Investigate the case

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• When the user tries to add assets which are already present then those assets will not be processed, and those assets are considered as duplicates.
• Access the portal click on review button which is right corner of ingestion.

• After clicking review button the asset page will open If same assets already exists in portal then those assets metadata will be merged and it will resolved automatically.

• Duplicate assets will merge all the metadata and it will be resolved automatically

• Screenshot of the error
• User Role
• Asset Name / Ingestion Name

• Check Network connection
• VPN connection
• Investigate the issue

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

1.3) Check network connectivity.

• access the portal and click on review button the below page will open and click on store front button to check the plagiarism.

• If plagiarism found, though you want to move those assets to DAM, just Click on ignore plagiarism check box those assets moved to DAM and if you click on plagiarism found check box those assets will moved to rejected tab.

• User ID
• What kind of role does the user need.

• Check role of the user &
• Role of the user request

• Check USER ID has roles or not. If there is no role assigned, then will assign the respective role to user.

Dear <user>,

Your request with Request ID: #______ has been parked into resolved state. Please re-open the request if you face this issue again.

Thanks, and regards,

Executive Name,

Executive Designation,

Executive Mobile Number.

• Ask URL from the requestor
• Screenshot of the error
• USER ID

• Check for the valid URL (URL: https://bccl.app.tenovos.io/  
• Check whether the VPN (Netskope Client) is connected
• Ensure that the link is accessible. 
• Check for the user role.
• Check the network from the user end.
• GCP Resources (SSO, User and Role collection)

• Verify the user credentials.

1.1. Ensure that the user is using the correct login credentials.

1.2 Confirm that the user has the necessary permissions for the assets in questionhttps://isca.bccl.in/


• Check the asset permissions.

2.1 Review the permissions assigned to the assets.Ensure that the user has the required access rights.

2.2 If permissions are role-based, confirm that the user is assigned to the appropriate role https://isca.bccl.in/

• Check the asset availability.

3.1 Ensure that the assets are accessible and available. Sometimes, access issues can be related to asset unavailability or technical problems

• User permissions

1.1 If User role doesn’t come under the specified permissions. We must let User know about it.

• User training

2.1 If the issue is related to user error or misunderstanding, provide training or documentation guide to the user on how to use “save search” option appropriately. .

• Ask URL from the requestor
• Screenshot of the error
• USER ID

• Check for the valid URL (URL: https://bccl.app.tenovos.io/  
• Check whether the VPN (Netskope Client) is connected
• Ensure that the link is accessible. 
• Check for the user role.
• Check the network from the user end.

• Check the User permissions.

1.1 Check the user's permissions. Ensure that the user has the necessary rights to create and manage collections. This includes both portal-wide permissions and specific permissions related to collections

• Review role and based access.

2.1 If your portal uses role-based access control, confirm that the user is assigned to a role that has the appropriate permissions for creating and managing collections

• Verify collection settings.

3.1 Review the settings and configuration for collections. Ensure that there are no restrictions or specific configurations that might be preventing the user from creating or managing collections

• Update the user role.

1.1, If the user lacks the necessary permissions, update their role to one that includes the appropriate collection management privileges

• User training.

2.1 If the issue was due to a user misunderstanding or error, provide training or documentation to help the user understand how to create and manage collections correctly

• Ask URL from the requestor
• Screenshot of the error
• USER ID

• Check for the valid URL (URL: https://bccl.app.tenovos.io/  
• Check whether the VPN (Netskope Client) is connected
• Ensure that the link is accessible. 
• Check for the user role.
• Check the network from the user end.

• Check the browser compatibility.

1.1. Verify that the user is using a supported and up-to-date web browser. Some portals may have browser compatibility issues, and using an outdated or unsupported browser can lead to problems.

• Test with another user id.

2.1 If the same issue arises from this profile also.

• User settings.

1.1 Let the User know what the settings need to be configured at browser level.

• Network issue.

2.1 It could be a network issue.

• User training.

3.1 If the issue is related to user error or misunderstanding, provide training or documentation to guide the user on how to save searches correctly

• Ask URL from the requestor
• Screenshot of the error
• USER ID

• Check for the valid URL (URL: https://bccl.app.tenovos.io/
• Check whether the VPN (Netskope Client) is connected
• Ensure that the link is accessible. 
• Check for the user role.
• Check the network from the user end.

• Check user reports.

1.1. Start by gathering information from users. Ask them to provide details about when the downtime occurred, any error messages they received, and specific issues they encountered.

• Verify downtime

2.1 Confirm that there is indeed downtime. Use monitoring tools or check with users to ensure that the platform is inaccessible or experiencing performance issues.

• Review recent changes

3.1 Check for recent changes or updates to the platform. Updates, configuration changes, or deployments can sometimes introduce issues that lead to downtime.

• Collaborate with IT Support

1.1. If the issue persists, involve IT support or portal administrators. They can investigate further, check server logs, and provide Insights into the problem.

• If portal Issue

2.1 It might be user traffic issue to portal. Ask User to check after 30 mins.

• Ask URL from the requestor
• Screenshot of the error
• USER ID
• Information related to new attributes

• Check for the valid URL (URL: https://bccl.app.tenovos.io/
• Check whether the VPN (Netskope Client) is connected
• Ensure that the link is accessible. 
• Check for the user role.
• Check the network from the user end.

• Verify whether the attributes required by the USER are already available in the portal.
• If not add the attributes or that particular asset.

• Inform USER that the similar attributes were already tagged for the specified asset.
• We have succeeded in adding the required attributes for that asset.

• Ask URL from the requestor
• Screenshot of the error
• USER ID

• Check for the valid URL (URL: https://bccl.app.tenovos.io/
• Check whether the VPN (Netskope Client) is connected
• Ensure that the link is accessible. 
• Check for the user role.
• Check the network from the user end.

• Gather detailed information

1.1 Talk to the user and gather detailed information about the requested role change. Understand the reasons behind the request, the specific changes they are looking for, and any immediate requirements.

• Review existing role and permissions.

2.1. Examine the user's current role and permissions. Understand what tasks and data access the current role allows and identify any limitations that might be prompting the user to request a change

• Communicate with IT or HR

3.1 If your organization has an IT or HR department, communicate with them to understand any broader implications of the role change. This may include changes in reporting structures, access controls, or compliance requirements

• Check role hierarchy

1.1, If your system has role hierarchies, consider the implications of the change on the user's position within the hierarchy. Ensure that the new role aligns with their responsibilities and the organizational structure

• Implement changes

2.1 Once all checks are complete and you are confident in the proposed role change, implement the changes in the system. Ensure that the user's profile is updated with the new role and permissions

• Ask URL from requestor.
• Screenshot of the error
• USER ID
• INGESTION NAME/assets name

• Check for the valid URL (URL: https://isca.bccl.in/)
• Check for connection with VPN (Netskope Client)
• Ensure the link is accessible.
• Check network from user end.
• Check browser.
• Investigate case.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• Find the ingestion with the name.

• Check the ingestion status.
• Check whether the ingestion(jobs) have finished the job status.
• Check if the job is rejected or if any duplication is found that job will not move into Tenovos.

• Need to do a manual review.

• Click on the REVIEW COMPLETE for every asset to check plagiarism check.
• After a successful plagiarism check, click on prepare then it will be able to sync to Tenovos.

• After clicking on the prepare button, in that ingestion, successful assets will move to Tenovos.
• Duplicated and rejected assets will remain in the portal under REJECTED TAB.

• Ask URL from requestor.
• Screenshot of the error
• USER ID
• INGESTION NAME/assets name

• Check for the valid URL (URL: https://isca.bccl.in/)
• Check for connection with VPN (Netskope Client)
• Ensure the link is accessible.
• Check network from user end.
• Check browser.
• Investigate case.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• find the ingestion with name that user provided, and check.
• The ingestion if it is created or not in isca portal. (example: asset#TSS-08112023).

• check that ingestion status.
• if it is not in COMPLETED status , that ingestion will not be able to sync assets to Tenovos.
• Assets in a job can be synced to Tenovos without a review being completed.
• Assets which do not require a review can be synced to Tenovos and assets in need of review can be reviewed later, which can be synced again post the review process.

• After successfully completing machine/manual enrichment.
• click on REVIEW COMPLETE and save for plagiarism check.
• Click on the REVIEW COMPLETE for every asset to check plagiarism check.
• After a successful plagiarism check, click on prepare then it will be able to sync to Tenovos.

• Check TENOVOS.

• Ask URL from requestor.
• Screenshot of the error
• USER ID
• INGESTION NAME/assets name

• Check for the valid URL (URL: https://isca.bccl.in/)
• Check for connection with VPN (Netskope Client)
• Ensure the link is accessible.
• Check network from user end.
• Check browser.
• Investigate case.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• check the asset with name which is given by user. (ex. Sify testing pattern).

• If user have only view access to ISCA PORTAL, he not able to update the custom attributes.

• For edit role access, ask him to contact ADMIN.

• Ask URL from requestor.
• Screenshot of the error
• USER ID
• INGESTION NAME/assets name

• Check for the valid URL (URL: https://isca.bccl.in/)
• Check for connection with VPN (Netskope Client)
• Ensure the link is accessible.
• Check network from user end.
• Check browser.
• Investigate case.

• Validate the error that which user gets.

1.1) Verify user with given link.

1.2) Login into ISCA PORTAL: https://isca.bccl.in/

• find the ingestion with name that user provided and check the Duplicate images.
• There is a possibility that any Similar image (META DATA) can be identified as duplicate

• If user have only view access to ISCA PORTAL, he not able to update the custom attributes.
• Check MD 5 Checksum field value is same for all similar images that are found.

• If an asset(image), is flagged is Duplicate and matches MD 5 Checksum value with another image(original).
• Then issue while pushing to DAM.
• In tenovos we cannot delate or edit.

• Job ID(type of the user)
• Ingestion Name
• Source/Source path
• Scheduled date
• Error Description
• Input parameters
• Collect the details

• Identify the problem
• Check for User Access and User role
• Check whether ingestion created or not by using ingestion name
• Check whether correct source path given or not
• Check whether the user scheduled date and time

• Validate the error that which user gets.

1.1) We check the user role

1.2) We have to check if the scheduler has enabled that particular ingestion or not: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• We have to check the time based upon the scheduled date and time.
• We must check job status

• Validate the error that which user gets.

1.3) We have to check the time based upon the scheduled date and time.

1.4) We must check job status: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.


1.5) Check Workflow Execution Steps (If the workflow has multiple steps, check which step is failing.)

1.6) Parameter verification.

• Change job scheduled date
• Will Provide respective user role against creating or processing jobs
• Retry failed job
• Communication with user
• Implement fixes

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date
• Asset Details

• Check for valid URL
• Check whether correct source path given or not
• Check for duplication image
• Check size of assets
• Check the source
• Check the format of assets
• Check Asset Metadata
• Check Asset Processing pipeline

• Validate the error that which user gets.

1.1) Check whether all assets are ingested successfully

1.2) Check in search in bar based upon the assets description/Title: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• check in All tab button whether that respected ingestion is available
• Check if there are any files with issues when processing
• Check for any differences in original files count and process files count
• Check for asset validation

• Check your network connection and try processing the assets.
• If there are no files count with issues, then we should reprocess the job
• Reprocess missing assets
• Communication with user

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date
• Sample images
• Detailed description of issue

• Check for user access and user role
• Manually provide more information
• Examine input data
• Check data quality

• Check Asset ID
• Check Parameter adjustment
• Locate the Application Log
• (Identify the location or system where your application logs are stored.)
• Check if vision API data available in the database for a specific asset
• Check application log if there is an error logged for that file

• Verify with users
• Documentation Updates
• Continuous Monitoring

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• First need to specify which state you got the error (open status, Upcoming status, auto enrich)
• Check whether ingestion created or not by using ingestion name
• Check whether correct source path given or not
• Review ingestion workflow

• Check if there are any files that have got issues for a specific job.
• Identify the Job (This could be a job ID, name, or any other unique identifier associated with the job.)
• Search for Job-related Entries

• Files with issues will be shown under error status
• Implement fixes
• Reprocess data
• Communication with users

• Job ID(type of the user)
• Ingestion Name
• Source/Source path
• Scheduled date
• Error Description
• Input parameters
• Collect the details

• Identify the problem
• Check for User Access and User role
• Check whether ingestion created or not by using ingestion name
• Check whether correct source path given or not
• Check whether the user scheduled date and time

• Validate the error that which user gets.

1.1) We check the user role

1.2) We have to check if the scheduler has enabled that particular ingestion or not: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• We have to check the time based upon the scheduled date and time.
• We must check job status

• Validate the error that which user gets.

1.3) We have to check the time based upon the scheduled date and time.

1.4) We must check job status: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.


1.5) Check Workflow Execution Steps (If the workflow has multiple steps, check which step is failing.)

1.6) Parameter verification.

• Change job scheduled date
• Will Provide respective user role against creating or processing jobs
• Retry failed job
• Communication with user
• Implement fixes

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date
• Asset Details

• Check for valid URL
• Check whether correct source path given or not
• Check for duplication image
• Check size of assets
• Check the source
• Check the format of assets
• Check Asset Metadata
• Check Asset Processing pipeline

• Validate the error that which user gets.

  1.1) Check whether all assets are ingested successfully

  1.2) Check in search in bar based upon the assets description/Title: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• check in All tab button whether that respected ingestion is available
• Check if there are any files with issues when processing
• Check for any differences in original files count and process files count
• Check for asset validation

• Check your network connection and try processing the assets.
• If there are no files count with issues, then we should reprocess the job
• Reprocess missing assets
• Communication with user

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• Check for user access and user role
• Manually provide more information
• Collect images which is facing error

• Identify Asset ID
• Identify Error Messages
• Locate the Application Log (Identify the location or system where your application logs are stored.)
• Check if vision API data available in the database for a specific asset
• Check application log if there is an error logged for that file

• If no vision API data found in the database, then reprocess the asset
• Identification of Missing Vision API Data (After querying the database and determining that no vision API data exists for the specified asset, you need to identify this absence in your application logic.)

• Job ID(type of the user)
• Ingestion Name
• Source/Source path
• Scheduled date
• Error Description
• Input parameters
• Collect the details

• Identify the problem
• Check for User Access and User role
• Check whether ingestion created or not by using ingestion name
• Check whether correct source path given or not
• Check whether the user scheduled date and time

• Validate the error that which user gets.

1.1) We check the user role

1.2) We have to check if the scheduler has enabled that particular ingestion or not: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• We have to check the time based upon the scheduled date and time.
• We must check job status

• Validate the error that which user gets.

1.3) We have to check the time based upon the scheduled date and time.

1.4) We must check job status: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.


1.5) Check Workflow Execution Steps (If the workflow has multiple steps, check which step is failing.)

1.6) Parameter verification.

• Change job scheduled date
• Will Provide respective user role against creating or processing jobs
• Retry failed job
• Communication with user
• Implement fixes

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date
• Asset Details

• Check for valid URL
• Check whether correct source path given or not
• Check for duplication image
• Check size of assets
• Check the source
• Check the format of assets
• Check Asset Metadata
• Check Asset Processing pipeline

• Validate the error that which user gets.

1.1) Check whether all assets are ingested successfully

1.2) Check in search in bar based upon the assets description/Title: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• check in All tab button whether that respected ingestion is available

• Check your network connection and try processing the assets.
• If there are no files count with issues, then we should reprocess the job
• Reprocess missing assets
• Communication with user

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• Check for user access and user role
• Manually provide more information
• Collect images which is facing error

• Identify Asset ID
• Identify Error Messages
• Locate the Application Log (Identify the location or system where your application logs are stored.)
• Check if vision API data available in the database for a specific asset
• Check application log if there is an error logged for that file

• If no vision API data found in the database, then reprocess the asset
• Identification of Missing Vision API Data (After querying the database and determining that no vision API data exists for the specified asset, you need to identify this absence in your application logic.)

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• Check your internet connection
• Check whether ingestion created or not by using ingestion name
• Check whether correct source path given or not

• Validate the error that which user gets.

1.1)If a duplicate file is identified, then job that has original file and the original file will be flagged to reprocess

• Parameter Validation (Ensure that they are accurate, up-to-date, and consistent with the requirements of the workflow)

1.2) We have to check if the scheduler has enabled that particular ingestion or not: https://isca.bccl.in/

• Reprocessing the asset is backend process, so check the application logs if there is any error with the file name
• Retry Reprocessing
• Communication with users

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• Check user role
• Ask what folder need to ignore
• Ask from which source user need to ignore the folder
• Review Processing Workflow

• Validate the error that which user gets.

1.1)Check if the source folders in popup have all the folder names that are there in storage bucket.

1.2)Check if there is empty folder in the storage bucket: https://isca.bccl.in/

• Access the portal and click on asset tab. Under the asset tab click on ingestion there is a filer option.

• Parameter Validation (Ensure that they are accurate, up-to-date, and consistent with the requirements for excluding specific folders)
• Configuration Adjustment (If the exclusion criteria are defined in configuration files, make adjustments as needed.)

• Any empty folder that is residing in the bucket will be shown in ISCA portal when it has got some files in it.
• Communication with user
• Documentation Updates (This ensures that future users have accurate and up-to-date information.)

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• Check for valid URL
• Check whether correct source path given or not
• Check for duplication image
• Check size of assets
• Check the source
• Check the format of assets

• Check whether all assets are ingested successfully
• Check in search in bar based upon the assets description.
• check in all tab button whether that respected ingestion is there or not.
• Check if there are any files with issues when processing
• Check for any differences in original files count and process files count

• Check your network connection and try processing the assets.
• If there are no files count with issues, then we should reprocess the job

• User ID
• URL
• Ingestion Name
• Source/Source path
• Scheduled date

• Check for valid URL
• Check for User Access and User role
• Check whether ingestion created or not by using ingestion name
• Check whether correct source path given or not
• Check whether the user scheduled correct or not

• Validate the error that which user gets.

We check the user role

• We must check if scheduler has enabled for that ingestion or not
• We have to check the time based open the scheduled date and time.
• We must check job status

• Will Provide respective user role against creating or processing jobs
• Change job scheduled date
• Change job status