-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CoE Starter Kit - BUG] Dataflows not working properly - null users coming from Data Export #7848
Comments
Is this for the client we have in active email about? If so can we please schedule? |
Yes. Will send a poll in a moment. Thank you again. |
Hey @Jenefer-Monroe, we noticed the following on the Makers Sync Cloud flow. Is this intentional? We suspect that this is not letting the dataflows do a full sync due to the terminate breaking the cycle. |
Hello yes this is known please see #7790 |
gotcha no worries. I got confused I thought it was for the February release instead of march. Thank you again for the prompt support. |
My bad for shipping it :D |
The above with both the changes to Maker and Flow as well as the adjustment to be sure they run in order is working now for the other enormous org I'm working with so I'm hopeful. |
We just implemented the changes. Now we are waiting for the dataflows to refresh. |
Dataflows are working as of now. However orphan apps are not being tagged properly. We suspect because the orphaned flow is being throttled. #7889 |
Does this bug already exist in our backlog?
Describe the issue
CoE BYODL Flows & CoE BYODL Makers Data flows are not working.
This is due to a mashup error related to the admin_maker entity.
Expected Behavior
Dataflows should run.
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.24
What app or flow are you having the issue with?
BYODL DataFlows Maker/Flow
What method are you using to get inventory and telemetry?
Data Export
Steps To Reproduce
No response
Anything else?
Reference:
#7719
#7648
AB#2566
The text was updated successfully, but these errors were encountered: