getScheduledTimestamp returns micro seconds not milliseconds

[longquanzheng]

https://github.com/uber/cadence-java-client/blob/14e523a7a0eae4b8ce671c07284da1c66261287c/src/main/java/com/uber/cadence/internal/sync/ActivityTaskImpl.java#L57

In Cadence server, timestamp is based on nanoSecond, not microSecond.

[jsferner]

No I never had any issues like that

On Wed, Feb 17, 2021 at 4:01 PM J. Hart [email protected] wrote:

I'm looking at this bug but my entire screen is lit up with "cannot resolve symbol" errors. Do you have the same issue? It's for the methods pertaining to these imports import com.uber.cadence.PollForActivityTaskResponse; import com.uber.cadence.WorkflowExecution; import com.uber.cadence.WorkflowType;

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/uber/cadence-java-client/issues/583#issuecomment-780850123, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANVZLECEWI5CWEHXF7E3VGTS7QVBHANCNFSM4XDQW3RQ .