Why the DB created by is empty?

hi bubble people…
I make a workflow to create something when the condition is true
but in database the created by field is empty !!
is there any situaion like this?

and when remove, add data range DB field sometimes it clear all the data ranges…
i have really big trouble like these, help me!

I don’t think anyone will be able to help you much with such a vague description of the problem, and without knowing a single thing about what you’re doing…

But in case like these, the only real way to find out what’s going wrong is to use the debugger and server logs.

So take a look at those, and you should be able to pinpoint the problem.

thanks!
(and i’m big fan of you, i was struggled with sticky style your post save me)
simply describe my problem is
if my DB have ( dateranges: 23/1/1-23/12/31, 24/2/1-24/5/1)
1 workflow) click something-> remove date range(23/1/1-23/12/31)->add daterange( 23/1/1-1/5)
this workflow perfectly work!
but it somtimes (click button fast) the DB’s dataranges become empty…

I think the only way the “created by” field will be empty is if the user who made the action wasn’t logged in.

Make sure you are logged in with a user and try again, if it persist, I recommend reaching out to bubble support.

Are you referring to the Created By or a Daterange field? You mentioned both but they are very different problems.

If you mean that the Daterange field is empty:
When the button is being clicked fast the workflows triggered might overlap and cause issues. Set up a custom state that makes the button unclickable as the first step fo the workflow, and set it back to empty at the end of the workflow, either in a custom workflow or setting ‘result of step X’ in the step’s contional (so that it gets triggered when the make change is actually completed)

If you mean that the ‘created by’ field is empty, @fuhclifffuhche 's comment+suggestion is the best shout.

Or if created by a webhook that doesn’t authenticate as a particular user. I just never use Created by and instead manually define a created by field for this reason.

thanks to everybody!
I think that created by field empty problem is my mistake…
but, the the date range (remove, add) sequentially by api workflow have some trouble…
so, i change my workflow to the other way