Production Ticket(ST) #11377: Snekku- Hi @Azhar13 why unable on behalf mn2? - Datanory - SNEKKU - Redmine

Production Ticket(ST) #11377

Snekku- Hi @Azhar13 why unable on behalf mn2?

Added by Muhammed Azhar Mohamed Maideen 6 months ago. Updated 5 months ago.

Status:

Ticket Resolved

Priority:

P2 - High

Assignee:

Muhammed Azhar Mohamed Maideen

Start date:

05/04/2024

Due date:

16/04/2024

% Done:

Estimated time:

Spent time:

2.00 h

Job Remark:

Ticket Logged Date:

05/04/2024

Ticket No.:

Related Ticket ID:

Type:

Support Request

SLA Initial Response:

05/04/2024

SLA Delivery:

Esclation Time:

Issue Reoccurance#:

Actual Initial Response:

15/04/2024

Resolution:

As we checked with customer. customer claimed that the issue was solved the activity done by customer they perform remove the app and redownload again and the customer claim that they able to perform the on behalf

case closed

Requester ExpectedDeliveryDate:

Delay Justification:

Priority Seq:

Effort (Hour):

External Ticket #:

None

Snekku_1.mp4 (4.41 MB) Snekku_1.mp4

Muhammed Azhar Mohamed Maideen, 05/04/2024 10:08 AM

History

#1 Updated by Muhammed Azhar Mohamed Maideen 6 months ago

Status changed from Assigned To to Support In Progress

#2 Updated by Muhammed Azhar Mohamed Maideen 6 months ago

File Snekku_1.mp4 Snekku_1.mp4 added
Status changed from Support In Progress to Pending Client Feedback

as we checked from out side there is no issue> upload as MN5 and perform the on behalf process and able to access for all user and able to display all planned and unplanned route

#3 Updated by Muhammed Azhar Mohamed Maideen 6 months ago

Already simulated from my side it still show the error
Already escaladed to shu ern for further checking the root cause
If login as MO able to see the customer list
If login as admin I could not see the customer list.

#4 Updated by Muhammed Azhar Mohamed Maideen 6 months ago

Due date changed from 08/04/2024 to 12/04/2024

Have to Run SQL profiler from our side for further checking

this is the root cause
The reason why the admin-on-behalf process couldn't view the customer list is because there are some invalid photos in the admin user , which caused a crash while accessing the database. Consequently, the process of retrieving the customer list halted. As a temporary workaround, user can utilize the MO user to do the send on behalf transaction after admin . The next deployment is scheduled for tomorrow.
hi shu ern is this correct?

Have to Run SQL profiler from our side for further checking