You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an orchestator that sends an object to an activity that includes strings that look like dates, from localhost (-05:00) if I send a date like '2021-03-15T16:00:00-07:00' it gets changed to '2021-03-15T18:00:00-05:00'.
A clear and concise description of what you expected to happen.
Actual behavior
A clear and concise description of what actually happened.
Relevant source code snippets
// insert code snippet here
Known workarounds
Provide a description of any known workarounds you used.
App Details
Durable Functions extension version (e.g. v1.8.3):
Azure Functions runtime version (1.0 or 2.0):
Programming language used:
Screenshots
If applicable, add screenshots to help explain your problem.
If deployed to Azure
We have access to a lot of telemetry that can help with investigations. Please provide as much of the following information as you can to help us investigate!
Timeframe issue observed:
Function App name:
Function name(s):
Azure region:
Orchestration instance ID(s):
Azure storage account name:
If you don't want to share your Function App or storage account name GitHub, please at least share the orchestration instance ID. Otherwise it's extremely difficult to look up information.
The text was updated successfully, but these errors were encountered:
Description
I have an orchestator that sends an object to an activity that includes strings that look like dates, from localhost (-05:00) if I send a date like '2021-03-15T16:00:00-07:00' it gets changed to '2021-03-15T18:00:00-05:00'.
Expected behavior
Actual behavior
Relevant source code snippets
// insert code snippet here
Known workarounds
App Details
Screenshots
If deployed to Azure
The text was updated successfully, but these errors were encountered: