personal car mileage

[monicavarela55]

A person is trying to enter the Personal Car Mileage expense in the application, but it is not allowing them to do so. The following error appears 6f2a4b8f-16d3-4802-bb4a-350ff11a9cfd

[KevinD]

@monicavarela55 SAP Concur has this as an issue and is currently working on it. I do not know the time line of the resolution though.

What is interesting is that it isn't affecting all users. I had no issue with adding car mileage. Did you try using a different browser? Maybe that will work.

[TriciaW]

@monicavarela55 

OPI-5885439

Started: Thursday, June 27, 2024 5:03 AM GMT-0600

Issue Identified Friday, June 28, 2024 9:00 AM GMT-0600

We have identified a degradation affecting your service. We have provided details of the incident known at this time below, and are currently assessing and verifying the full extent of the user impact and assembling a specialized Incident Response Team (IRT) to investigate and resolve the issue. We will post the next incident communication at or before 09:30 PM UTC on 28 Jun 2024. In the US2 and EU2 Data Centers, saving car mileage expenses through the SAP Concur website is below expected level. Affected users may experience the following error when attempting to save a car mileage expense entry, "Sorry, but something went wrong with this task.

Issue Status Update Friday, June 28, 2024 3:20 PM GMT-0600

As previously reported, we have identified a degradation affecting your service. An Incident Response Team (IRT) with expertise specific to this issue has been assembled and they have verified the impact on user experience. Details on user impact and our current action plan are provided below. We will post the next incident communication at or before 3:30AM UTC on 02 July 2024. In the US2 and EU2 Data Centers, saving car mileage expenses through the SAP Concur website is below expected level. Affected users may experience the following error when attempting to save a car mileage expense entry, "Sorry, but something went wrong with this task." A workaround for this issue is not available at this time. The Incident Response Team has triaged the issue and begun investigation to identify root cause.