# How to overcome this ( Transaction has 24 milliseconds difference of event in apm rum js and apm php agent )

**URL:** https://discuss.elastic.co/t/how-to-overcome-this-transaction-has-24-milliseconds-difference-of-event-in-apm-rum-js-and-apm-php-agent/365662
**Category:** APM
**Tags:** docker, rum, php
**Created:** [August 28, 2024, 7:47am UTC](https://discuss.elastic.co/t/how-to-overcome-this-transaction-has-24-milliseconds-difference-of-event-in-apm-rum-js-and-apm-php-agent/365662 "2024-08-28T07:47:04Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![kishorkumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kishorkumar/32/132930_2.png) [@kishorkumar](https://discuss.elastic.co/u/kishorkumar)
#### Post date: [August 28, 2024, 7:47am UTC](https://discuss.elastic.co/t/how-to-overcome-this-transaction-has-24-milliseconds-difference-of-event-in-apm-rum-js-and-apm-php-agent/365662/1 "2024-08-28T07:47:04Z")

</div>

i have php agent installed in WordPress docker container and in frontend i have added rum js,

now when my user visits the the shop page or my-account, php agent runs first to create first , my frontend rum js transaction is rapidly ingested into elastic but backend is taking 24 milliseconds - above in @timestamp field and its being ingested very late like after 1 minute in my elastic index.

as you can see below the records and also the trace.id is different ?

what is the disadvantages of having different trace.id for same transaction

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/1/d17600a98ab4091e8eab41d18e85f7843a2ec9d8.png)

#Elastic Observability #APM #rum #php