Skip to main content
Question

MWO Failed Report In

  • June 24, 2025
  • 3 replies
  • 80 views
M
Do Gooder (Customer)
Forum|alt.badge.img+5

We have a couple of assignments connected to different work tasks and users all with the same error.

Time has already been reported against the assignment, and we’re just trying to set it to completed status.
 

We’re now stuck in a loop - we can’t un-transfer the assignment from MWO, and we can’t complete it in IFS since it’s transferred to MWO.

 

What’s the cause of this error and how can we complete the assignment?

 

Error

Action<ReportInVirtual.ReportIn>: Failed to assign value to Clocking.EmployeeId. Value = (employeeno)

 

 

3 replies

C
Do Gooder (Customer)
Forum|alt.badge.img+7

Hi,

 

we have the same issue here:
 

 

The error disappeared after removing the “Add Return Travel” from the Report In window.
Of course these times are then not on the protocol.

Is there any feedback on this error?

 

Regards, 

S
Do Gooder (Partner)
Forum|alt.badge.img+4
  • SAWI
  • Do Gooder (Partner)
  • December 17, 2025

​@Bandula 

We have same issue as Failed Transaction,

Instance of entity REPORT_IN_VIRTUAL with objid [9012F5C45A744FDEA063D5F4EC2FF11C] not found in database

Do you know any issue related to this already reported ?

Bandula
Hero (Employee)
Forum|alt.badge.img+12
  • Bandula
  • Hero (Employee)
  • December 17, 2025

Hi, 

These types of errors in Virtuals are difficult to diagnose without identifying the root cause. We need to review the client logs and synchronization traces to get better insight.

If the issue is still occurring, it would be best to raise a support ticket. If required, we can also provide a data script to recover any stuck work assignments.

Terms & ConditionsCookie settingsAccessibility statement