[DONE] Error when using created on in conditional

[joao.matheus]

Hello, I have a problem every time I call a field created on an automation it returns this error.

my if is this

[tomaz]

It is hard to help without seeing your automation.
But my guess is you are calling a date field that is not populated on create. Automation returns empty and this could cause en error.
Like I said, guessing, hard to tell without seeing automation.

[joao.matheus]

Thank you very much for your help but
the action with the error is this if no print
and the field is a created on type that is automatically updated upon creation

[tomaz]

If I understand it correctly…
you are running automation on create, right?
And you are using created on field?
If that is correct I don’t understand the logic and what are you trying to achieve, because you are using conditional on create +2 days which doesn’t make sense to me.
Maybe explain more what are you trying to do accomplish.

[joao.matheus]

I understand your question, it is a scheduled flow that will run every day to check if we have items with overdue completion.

[tomaz]

Since we don’t have the the whole automation to better understand the issue, maybe a little quick workaround: add new date filed. Update it when record is created +2 days. Create filter view with that date field and save it as a view.
Use that view on runs to check all overdue records…
hope this helps.

[Jason]

@joao.matheus has sent me some more details and this is replicate able:

[Jason]

@joao.matheus

Sorry, I ran out of time yesterday however if you want to get it working while the Tape team are looking at it then I believe the following will work for you:
First of all change your conditional filter into a script:

then make some changes:

1. You can remove the undefined time on the current dateline
2. you can remove the time on the created at-time
3. Replace the value with your collected variable. This certainly stops the error, and I think it will give the result you want, but you should check as that is hard for me to do.
4. You should end up with something like:

TapeUtils.isDateEqual(
    { date: collected_action_created_at_date },
    { date: current_date_local},
    current_workflow_timezone,
    { offset_operator: 'MINUS', offset_amount: (2) ?? 0 }
    )

also as we discussed your ‘offset’ needs to be MINUS not PLUS

Hope that helps

[Leo]

Hi @joao.matheus,

thank you very much for reporting the issue and many many thanks to @tomaz and @jason for the great support in debugging the issue.

According to Jason’s analysis, we assume that there is an issue in the code generation of the filter, we are already checking and trying to roll out a fix today.

We will get back to you here as soon as we have new findings or the issue is fixed.

Best regards
Leo

[Tim]

Thanks for your report @joao.matheus. Additional thanks for diving into this @Jason and providing the workaround.

Indeed, this is a confirmed bug on our side. Fix incoming - will let you know once it’s live.

Cheers
Tim

EDIT: The fix is already live. Could you confirm that this is working as expected now?

[Sameer]

Hi @Jason if you could help me to sort this out…That’s seems to be quite similar but unable to sort this…The filter not running and so the action not being triggered

[Jason]

Hi @Sameer

I am on my phone so bear with me, it looks like your offsets are wrong the first (after) should be -1 and the second (before) should be +1.

That assumes you are after ‘today’

Let me know if I have understand correctly and if not I can have a better look later.

Jason

[Sameer]

TBH, I’m on my way to learn the Tapeapp, So the idea was to check the Scheduled Date > Current Date…And I just did something this and verifying it…If you could let me know, it’s correct what I’m hoping? If not then what this does so I can have an idea about it…
Moreover, is there any guide available to learn these things…Like I know about Podio, they have PWA guideline here https://workflow-automation.podio.com/help/
Thanks for your time

[Leo]

Hi @Sameer,

great to hear that you’re diving into learning Tape automations, that’s really exciting!

Most of our help articles for automations are collected right here in the community. There’s an overview article you can start with here, and from there you’ll also find dedicated sections:

Triggers: Here

Filters: Here

Actions: Here

On top of that, we also have a library of showcases that you can duplicate directly into your own Tape workspace. These are super useful because you can experiment hands-on with real examples and learn by trying them out.

I think you’ll find plenty of inspiration and practical guidance in those resources.

Best regards,
Leo